ci4-cms-erp/ci4ms
Affected
- introduced
0, fixed0.31.0.0(ecosystem)
Fixed versions
0.31.0.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-34563
CI4MS: Backup Management Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM Blind XSS
Summary
Vulnerability: Stored DOM Blind XSS via Backup Management Filename (Persistent Payload Injection)
Description
The application fails to properly sanitize user-controlled input when handling backup uploads and processing backup metadata. An attacker can inject a malicious JavaScript payload into the backup filename via the uploaded xss.sql, which uses SQL functionality to insert the XSS payload server-side.
This stored payload is later rendered unsafely in multiple backup management views without proper output encoding, leading to stored blind cross-site scripting (Blind XSS).
Affected Functionality
Attack Scenario
xss.sql which uses SQL functionality to insert a malicious XSS payload into the backup filename field server-side.Impact
Endpoints:
/backend/backup/upload/backend/backup//backup/{id}Steps To Reproduce (POC)
xss.sql via the Backup Upload functionality<img src=x onerror=alert(document.domain)>
Remediation
.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.HttpOnly attribute on session cookies to prevent client-side script access.SameSite cookie attribute to mitigate Cross-Site Request Forgery (CSRF) risks.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/eNFXgAAA#IETbPcKwr5vVLqJIAdc3uy4qgcVTgyPb_2HhB4zcwAE
Critical Basis: The source's own band: CRITICAL
0, fixed 0.31.0.0 (ecosystem)0.31.0.0
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0