GHSA-v897-c6vq-6cr3: CI4MS: System Settings (Company Information) Full Platform Compromise & Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS
Summary**Vulnerability: Stored DOM XSS via System Settings – Company Information (Same-Page Attribute Breakout & Persistent Payload Injection)**Stored Cross-Site Scripting via Unsanitized Company Information Configuration Fields with Immediate Same-Page ExecutionDescriptionThe application fails to properly sanitize user-controlled input within **System Settings – Company Information**. Several administrative configuration fields accept attacker-controlled input that is stored server-side and later rendered without proper output encoding.Affected fields include, but are not limited to:Company NameSloganCompany PhoneCompany MobileCompany EmailGoogle Maps iframe linkCompany Logo and other media-related fieldsUnlike the public-facing landing page injection vulnerability, this issue executes directly on the same settings page. The injected payload breaks out of the HTML attribute context and is immediately interpreted by the browser when rendered, resulting in same-page DOM-based stored XSS.This represents different functionality and a separate vulnerability from public-facing rendering.Affected FunctionalitySystem Settings – Company Information configurationSame-page rendering of user-controlled input fieldsDOM attribute injection within form inputsStorage and retrieval of company information valuesAttack ScenarioAn attacker injects a malicious JavaScript payload into one or more Company Information fields.The payload breaks out of the HTML attribute context.The application stores and re-renders the payload without sanitization or encoding.The payload executes immediately on the same settings page.The script executes in the browser context of the authenticated user managing settings.ImpactPersistent Stored XSSImmediate Same-Page DOM XSS executionExecution of arbitrary JavaScript in victims’ browsersAdministrative privilege escalationFull administrator account takeoverFull account takeover across all rolesFull compromise of the entire platformEndpoints:`/backend/settings/` (Company Information)Steps To Reproduce (POC)Navigate to System Settings -> Company InformationInsert the following XSS payload into any Company Information field:
`test"><img src=1 onerror=alert()>" class="form-control" placeholder="Name" required>`Save the settingsObserve that the payload breaks out of the input attribute contextThe XSS executes immediately on the same pageRemediation**Avoid unsafe DOM manipulation methods:** Do not use `.html()`, `innerHTML`, or similar sink functions in client-side JavaScript or server-side templating (e.g., PHP). Even when user input flowing into these sinks is not immediately apparent, they can introduce Cross-Site Scripting (XSS) vulnerabilities that an attacker may exploit.**Apply output encoding:** Implement HTML entity encoding on all user-controlled data before rendering it in the browser. This helps neutralize potentially malicious input.**Implement input sanitization:** Ensure that all user-supplied input is properly sanitized before processing or output. Currently, no sanitization mechanisms are in place, which should be addressed as a priority.**Enforce security headers and cookie attributes:****Content Security Policy (CSP):** Define and enforce a strict CSP to limit the execution of unauthorized scripts.**HttpOnly flag:** Set the `HttpOnly` attribute on session cookies to prevent client-side script access.**SameSite attribute:** Configure the `SameSite` cookie attribute to mitigate Cross-Site Request Forgery (CSRF) risks.**Secure flag:** Ensure all cookies are transmitted only over HTTPS by enabling the `Secure` attribute.These measures collectively reduce the impact of XSS and help prevent escalation paths such as CSRF via XSS.Ready Video POC:https://mega.nz/file/qEcFUIjR#2OKX78JgPQI2x5957GE-vx1zYzJv2a9JqjyBsrRFBkk
CVSS v3.1: 4.7