Document Title: =============== 8Pixel Blog CMS v4.2 - Cross Site Scripting Vulnerability Release Date: ============= 2011-08-14 Vulnerability Laboratory ID (VL-ID): ==================================== 1 Product & Service Introduction: =============================== 8pixel.net developes applications for the .NET platform. We develop browser based, windows applications and combinations of both. As well we provide some apps for download, such as 8pixel.net blog v4. (Copy of the Vendor Homepage: http://8pixel.net/) Abstract Advisory Information: ============================== The Vulnerability-Lab Team discovered multiple persistent Cross-Site-Scripting Vulnerability on 8Pixel Blog v4.2 Remote attackers can implement malicious persistent script code on a main software module of the blog/cms. Vulnerability Disclosure Timeline: ================================== 2011-08-15: Discovery by Vulnerability-Lab Discovery Status: ================= Published Affected Product(s): ==================== Exploitation Technique: ======================= Remote Severity Level: =============== High Technical Details & Description: ================================ A XSS(Cross-Site-Scripting) vulnerability is detected on 8Pixel Blog v4.x. Remote attackers can include persistent malicious script codes on application-side. When sucessfully exploited by an authenticated user, the identified vulnerabilities can lead to Information Disclosure, Session Hijacking, access to Web Interface. Its also possible to load malware or scripts out of the comment context of the website. Vulnerable Module(s): [+] Comments - E-Mails & Names Proof of Concept (PoC): ======================= The vulnerability can be exploited by local restricted user or remote attackers without auth. The vulnerability can reproduced by the following way/example ... Methods: [+] XSS Restriction Bypass - Cross-Site-Scripting 1. Open the Blog Website 2. Open a post and switch to the comments under the article 3. Implement your malicious persistent script on the vulnerable input fields (name & email) 4. After saving the input is persistent implemented on application-side 5. Malicious script code will be executed on every request of the article by users/administrators PoC: >"