Loading...
Skip to main content

CVE-2026-34560

CRITICAL

CI4MS: Logs Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS

Published April 1, 2026Updated April 6, 2026Source: osv

Summary

## Summary ### **Vulnerability: Stored DOM Blind XSS via Logs Interface Rendering (Administrative Context Execution)** - Stored Cross-Site Scripting (Blind XSS) via Unsafe Rendering of User-Controlled Logged Data ### Description The application renders user-controlled input unsafely within the logs interface. If any stored XSS payload exists within logged data, it is rendered without proper output encoding. This issue becomes a Blind XSS scenario because the attacker does not see immediate execution. Instead, the payload is stored within application logs and only executes later when an administrator views the logs page. For example, accessing `/backend/backup/restore/xss-payload-here` causes an error that gets logged by the application. If the injected portion contains an XSS payload, it is stored inside the logs without sanitization and later rendered unsafely inside the logs management interface. When an administrator views the logs page, the stored payload executes automatically in the administrative browser context, leading to stored blind cross-site scripting (Blind XSS). ### Affected Functionality - Application logging mechanism - Logs storage and retrieval logic - Logs rendering within administrative interface - Any endpoint that logs unsanitized user-controlled input ### Attack Scenario - An attacker injects a malicious XSS payload into any user-controlled input that is logged by the application. - Example: Visit `/backend/backup/restore/<img src=x onerror=alert(document.domain)>` - The application throws an error and logs the malicious payload. - The payload is stored within application logs. - An administrator views the logs interface. - The payload executes automatically in the administrator’s browser context. Any method or endpoint that logs user-controlled input without sanitization will result in the same Blind XSS condition when viewed inside logs management. ### Impact - Persistent Stored Blind XSS - Execution of arbitrary JavaScript in administrators’ browsers - Privilege escalation when viewed by administrators - Full administrator account takeover - Full compromise of the entire application Endpoints: - `/backend/logs/` - `/backend/backup/restore/{payload}` - Any other endpoint that logs xss payloads there ## Steps To Reproduce (POC) 1. Trigger an endpoint that logs user-controlled input, such as: `/backend/backup/restore/<img src=x onerror=alert(document.domain)>` 2. Ensure the request generates an error and the payload is written into application logs 3. Navigate to the logs interface as an administrator 4. View the logged entry 5. Notice the XSS payload executing automatically (Blind XSS) ## 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 `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/jRN3nDSR#wJCwyFhbeT-OYAwlaTD_7j6wc5wRgz1EGJL0bnuhHxY

Remediation

Upgrade to the fixed version using your package manager.

Composer
Update ci4-cms-erp/ci4ms to 0.31.0.0 or later
composer require "ci4-cms-erp/ci4ms:^0.31.0.0"

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

PackageEcosystemAffectedFixed In
ci4-cms-erp/ci4ms
packagist
0.21.0, 0.21.1, 0.21.2, 0.21.3 (+43 more)0.31.0.0

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-79
    Cross-site Scripting (XSS)MITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.1 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

Frequently Asked Questions

What is CVE-2026-34560?
CI4MS: Logs Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.1/10).
How do I check if my project is affected by CVE-2026-34560?
CVE-2026-34560 affects ci4-cms-erp/ci4ms. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-34560 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
9.1

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-r4v5-rwr2-q7r4

Related CVEs

  • CVE-2026-34566
    CRITICAL

    CI4MS: Pages Management Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS

  • CVE-2026-35035
    CRITICAL

    CI4MS: Company Information Public-Facing Page Full Platform Compromise & Full Account Takeover for All Roles & Privilege-Escalation via System Settings Company Information Stored DOM XSS

  • CVE-2026-27599
    CRITICAL

    ci4-cms-erp/ci4ms: System Settings (Mail Settings) Full Platform Compromise & Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS

  • CVE-2026-34563
    CRITICAL

    CI4MS: Backup Management Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM Blind XSS

  • CVE-2026-34571
    CRITICAL

    CI4MS: Stored Cross‑Site Scripting (Stored XSS) in Backend User Management Allows Session Hijacking and Full Administrative Account Compromise

  • CVE-2026-34569
    CRITICAL

    CI4MS: Blogs Categories Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS

  • CVE-2026-34570
    HIGH

    CI4MS: Account Deletion Module Grants Full Persistent Unauthorized Access for All‑Roles via Improper Session Invalidation (Logic Flaw)

  • CVE-2026-34572
    HIGH

    CI4MS: Account Deactivation Module Grants Full Persistent Unauthorized Access for All‑Roles via Improper Session Invalidation (Logic Flaw)

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies