GHSA-xgh5-w62m-8mpr
CRITICALGHSA-xgh5-w62m-8mpr is a critical-severity (CVSS 9.1) Cross-site Scripting (XSS) vulnerability in ci4-cms-erp/ci4ms. O3 Security confirms whether GHSA-xgh5-w62m-8mpr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CI4MS: Menu Management (Posts) Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS
Real-World Exposure
ci4-cms-erp/ci4msReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Vulnerability: Stored DOM XSS via Posts Added to Menu (Persistent Payload Injection)
- Stored Cross-Site Scripting via Unsafe Rendering of Post Entries in Menu Management
Description
The application fails to properly sanitize user-controlled input when adding Posts to navigation menus through the Menu Management functionality. Post-related data selected via the Posts section is stored server-side and rendered without proper output encoding.
These stored values are later rendered unsafely within administrative dashboards and public-facing navigation menus, resulting in stored DOM-based cross-site scripting (XSS).
Affected Functionality
- Menu Management – Posts section
- Adding posts to navigation menus
- Menu storage and rendering logic
Attack Scenario
- An attacker creates or controls a post containing a malicious JavaScript payload.
- The attacker adds the post to the menu using the Posts functionality in Menu Manager.
- The application stores the menu entry without sanitization or encoding.
- The payload persists and executes whenever the menu is rendered.
Impact
- Persistent Stored DOM XSS
- Execution of arbitrary JavaScript in victims’ browsers
- Privilege escalation in administrative contexts
- Full administrator account takeover
- Full account takeover across all roles
- Full compromise of the entire application via global navigation execution
Endpoint:
/backend/menu/
Steps To Reproduce (POC)
- Navigate to Menu Management
- Use the Posts section to add a post containing an XSS payload such as:
<img src=x onerror=alert(document.domain)> - Save the menu
- View the menu in the administrative panel or any public-facing page
- Observe the JavaScript payload executing automatically
Remediation
-
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
HttpOnlyattribute on session cookies to prevent client-side script access. - SameSite attribute: Configure the
SameSitecookie attribute to mitigate Cross-Site Request Forgery (CSRF) risks. - Secure flag: Ensure all cookies are transmitted only over HTTPS by enabling the
Secureattribute.
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/PcMiUA5K#L2RlZJa340Q8K42TksxiXMuo_9XsRYPi14-WvBnak2A
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ci4-cms-erp/ci4ms | all versions | 0.31.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ci4-cms-erp/ci4ms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ci4-cms-erp/ci4ms to 0.31.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xgh5-w62m-8mpr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xgh5-w62m-8mpr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-xgh5-w62m-8mpr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xgh5-w62m-8mpr in your dependencies?
O3 detects GHSA-xgh5-w62m-8mpr across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.