[FD] Exponent CMS 2.3.9 - Useraccounts Persistent Vulnerability

Document Title: =============== Exponent CMS 2.3.9 - Useraccounts Persistent Vulnerability References (Source): ==================== http://ift.tt/2ausNvL Release Date: ============= 2016-07-27 Vulnerability Laboratory ID (VL-ID): ==================================== 1886 Common Vulnerability Scoring System: ==================================== 4.5 Product & Service Introduction: =============================== Exponent is a web application that allows site owners to easily create and manage dynamic websites. Unlike other site management tools, Exponent is completely self-contained. No additional applications need to be downloaded by a user to permit them to use Exponent. Everything from user management to site configuration to content editing and approval is done within the system. (Copy of the Vendor Homepage: http://ift.tt/1CTRvbI ) Abstract Advisory Information: ============================== The vulnerability laboratory core research team discovered a persistent input validation vulnerability in the official Exponent v2.3.9 open-source content management system. Vulnerability Disclosure Timeline: ================================== 2016-07-27: Public Disclosure (Vulnerability Laboratory) Discovery Status: ================= Published Affected Product(s): ==================== Exponent Community Product: Exponent - Content Management System (Open Source) 2.3.9 Exploitation Technique: ======================= Remote Severity Level: =============== Medium Technical Details & Description: ================================ An application-side input validation web vulnerability has been discovered in the official Exponent v2.3.9 open-source content management system. The vulnerability allows remote attackers to inject own malicious script codes on the application-side of the vulnerable module or affected function. The vulnerability is located in the `firstname` and `lastname` parameters of the `useraccounts` module. The vulnerable inputs are `realname` and `user`. Remote attackers are able to use the registration to inject own malicious script codes to the backend of the exponent web-application. The injection points are the vulnerable `createuser` and `umgr_editprofile` of the user manager and the execution point occurs in the `useraccounts` module. The request method to inject is POST and the attack vector is persistent on the application-side. The vulnerability can be exploited by local privileged user account or remotly by anonymous users via basic registration. The execute in the useraccounts module occurs on visit of the page module via backend by the administrator account. The security risk of the application-side web vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 4.7. Exploitation of the vulnerability requires a low privileged web-application user account (registration or create) and only low user interaction. Successful exploitation of the vulnerability results in session hijacking, persistent phishing attacks, persistent external redirects to malicious source and persistent manipulation of affected or connected application modules. Request Method(s): [+] POST Vulnerable Module(s): [+] createuser (basic user account) [+] umgr_editprofile (admin account) Vulnerable Parameter(s): [+] firstname [+] lastname Affected Module(s): [+] ./useraccounts Proof of Concept (PoC): ======================= The persistent input validation vulnerability can be exploited by remote attackers with privileged web-application user account and with low user interaction. For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue. Inject: Add or Register Account URL: http://ift.tt/2acXNeP URL: http://ift.tt/2apytpo Execution: User Accounts URL: http://ift.tt/2acYcy7 Manual steps to reproduce the vulnerability ... 1. Open the vulnerable cms website with the affected version 2. Surf to the user registration that is open by default 3. Include as realname and user name a script code payload (firstname & lastname) 4. Save the registration via POST method request Note: The user account arrives visible in the user accounts management of the exponent cms (admin backend) 5. Now the admin login to his application and only needs to watch the user accounts management to execute the payload 6. Successful reproduce of the vulnerability! PoC: User Accounts Management Listing

Source: Gmail -> IFTTT-> Blogger

Real Name
[REALNAME PERSISTENT SCRIPT CODE EXECUTION!]	[USER PERSISTENT SCRIPT CODE EXECUTION!]	asdasdasda@mail.com	a