GHSA-fc4p-p49v-r948
CRITICALGHSA-fc4p-p49v-r948 is a critical-severity (CVSS 9.9) Cross-site Scripting (XSS) vulnerability in ci4-cms-erp/ci4ms. O3 Security confirms whether GHSA-fc4p-p49v-r948 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CI4MS: Stored Cross‑Site Scripting (Stored XSS) in Backend User Management Allows Session Hijacking and Full Administrative Account Compromise
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
A critical Stored Cross-Site Scripting (Stored XSS) vulnerability exists in the backend user management functionality. The application fails to properly sanitize user-controlled input before rendering it in the administrative interface, allowing attackers to inject persistent JavaScript code. This results in automatic execution whenever backend users access the affected page, enabling session hijacking, privilege escalation, and full administrative account compromise.
Details
The vulnerability resides in the backend user creation feature accessible via:
/backend/users
User-supplied input in the name and surname fields is stored without proper validation or sanitization. When this data is later rendered in the backend users listing page, it is injected directly into the HTML without output encoding.
Because of this, attackers can embed malicious JavaScript payloads that execute in the context of authenticated backend users.
This indicates missing contextual output escaping (e.g., HTML encoding) and insufficient input sanitization, leading to persistent script execution.
The vulnerability is particularly severe because:
- The payload is stored in the database (persistent XSS).
- The script executes automatically on page load.
- The affected page appears to be an administrative/backend interface, increasing the risk of privilege escalation.
PoC
Steps to reproduce:
- Navigate to:
http://localhost:8080/backend/users
-
Click Add New User.
-
Create a new user.
-
In the name and surname fields, insert the following payload:
adnan"><img src=1 onerror=alert(document.cookie)><<e>img src=1 onerror=alert(document.cookie)>
-
Save the user.
-
After saving, a popup displaying cookies will appear, demonstrating JavaScript execution.
-
Revisit:
http://localhost:8080/backend/users
- The popup automatically triggers again, confirming that the malicious script is stored and executed persistently. <img width="1534" height="834" alt="image" src="https://github.com/user-attachments/assets/83f3d124-cf2e-472d-87cc-8c668ea81cba" />
Impact
Severity: Critical
This vulnerability enables:
- Persistent execution of attacker-controlled JavaScript in privileged backend contexts.
- Theft of session cookies, potentially leading to full account takeover.
- Unauthorized actions performed on behalf of administrators (CSRF-like behavior via XSS).
- Privilege escalation if a high-privilege user views the page.
- Injection of keyloggers, credential harvesting scripts, or malicious redirects.
- Full compromise of backend administrative functionality depending on role permissions.
Since the payload executes automatically without user interaction once stored, exploitation requires minimal effort and can impact all backend users.
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-fc4p-p49v-r948 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-fc4p-p49v-r948 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-fc4p-p49v-r948. 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-fc4p-p49v-r948 in your dependencies?
O3 detects GHSA-fc4p-p49v-r948 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.