[FD] Habari CMS v0.9.2 - (Backend Comments) XSS Vulnerability

Document Title: =============== Habari CMS v0.9.2 - (Backend Comments) XSS Vulnerability References (Source): ==================== http://ift.tt/2fClouO Release Date: ============= 2016-11-09 Vulnerability Laboratory ID (VL-ID): ==================================== 1999 Common Vulnerability Scoring System: ==================================== 3.5 Product & Service Introduction: =============================== While there are a number of technical reasons that highlight the differences and advantages Habari has over other blogging packages, a major component of what makes Habari different is its community participation model. (Copy of the Homepage: http://ift.tt/2g4vH9t ) Abstract Advisory Information: ============================== The vulnerability laboratory core research team discovered a persistent cross site scripting vulnerability in the Habari v0.9.2 content management system. Vulnerability Disclosure Timeline: ================================== 2016-11-09: Public Disclosure (Vulnerability Laboratory) Discovery Status: ================= Published Affected Product(s): ==================== Habari Product: Habari - Content Management System 0.9.2 Exploitation Technique: ======================= Remote Severity Level: =============== Medium Technical Details & Description: ================================ A persistent cross site scripting web vulnerability has been discovered in the official Habari CMS v0.9.2. The vulnerability allows remote attackers to inject own malicious script code on the application-side of affected web modules or service function. The persistent cross site scripting web vulnerability is located in the `name` parameter of the `comments` module. Remote attackers without privileged web-application user accounts are able to inject malcious script code to the comments backend. Thus allows remote attackers to execute script code on preview of the comments section for administrators in the application backend. The attack vector of the issue is persistent and the request method to inject the malicious comments is POST. The vulnerability is a classic cross site scripting issue that affects the backend to compromise administrator accounts. The security risk of the issue is estimated as medium with a cvss (common vulnerability scoring system) count of 3.5. Exploitation of the web vulnerability requires no privileged web-application user account and only low user interaction. Successful exploitation of the vulnerability results in persistent phishing attacks, session hijacking, persistent external redirect to malicious sources and persistent manipulation of affected or connected web module context. Request Method(s): [+] POST Vulnerable Module(s): [+] Feedback - Comments Vulnerable Parameter(s): [+] comment_name Affected Module(s): [+] Backend - Comments Proof of Concept (PoC): ======================= The vulnerability can be exploited by remote attackers without user account and with low user interaction. For security demonstration or to reproduce follow the provided information and steps below to continue. Manual steps to reproduce the vulnerability ... 1. Open the application with an article 2. Write a comment and include as name to the comment a script code payload 3. Save to submit via POST method request Note: Now the attacker awaits the admin watches the comments 4. The malicious script code payload executes on visit of the comments module in the backend 5. Successful reproduce of the remote vulnerability! Injection Point: http://ift.tt/2fCkkqK Execution Point: http://ift.tt/2g4AlnO PoC: Exploitation (comment_name)

<[PAYLOAD EXECUTION VIA NAME OF THE COMMENTS INPUT!]>

test message by pentester

2016-11-05 8:05 pm

Source: Gmail -> IFTTT-> Blogger