CVE-2026-34567: CI4MS Cross-Site Scripting Vulnerability
CRITICALCVE-2026-34567 is a CRITICAL (CVSS 9.1) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting CI4MS libraries in the Packagist ecosystem. The issue involves blogs posts (categories) full account takeover for all-roles & privilege-escalation via stored dom xss. Remediation is available by upgrading affected packages to version 0.31.0.0.
CVE-2026-34567 at a Glance
Security Impact
CVSS: 9.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L).
How to Fix CVE-2026-34567
To remediate this vulnerability, upgrade all affected CI4MS dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade ci4-cms-erp/ci4ms to 0.31.0.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for ci4-cms-erp/ci4ms
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-34567, inspect your project dependencies for CI4MS:
inspect dependencies for ci4-cms-erp/ci4ms
Analyze the terminal output to locate any version of CI4MS in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.31.0.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In CI4MS, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-34567 Affected CI4MS Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
ci4-cms-erp/ci4ms
|
Packagist |
< 0.31.0.0
|
0.31.0.0
|
References
Frequently Asked Questions
What is CVE-2026-34567?
Which CI4MS versions are affected?
What version fixes CVE-2026-34567?
Is ci4-cms-erp/ci4ms affected?
What is the CVSS score of CVE-2026-34567?
What CWE is associated with CVE-2026-34567?
How can I check Packagist dependencies for CVE-2026-34567?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-r33w-c82v-x5v7",
"modified" : "2026-04-06T17:14:31Z",
"published" : "2026-04-01T22:06:50Z",
"aliases" : [ "CVE-2026-34567" ],
"summary" : "CI4MS: Blogs Posts (Categories) Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS",
"details" : "# Summary \n### **Vulnerability: Blogs Posts (Categories) Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS**\n- Stored Cross-Site Scripting via Unsanitized Blog Post Content in Blog Management (Categories)\n\n### Description\nThe application fails to properly sanitize user-controlled input when creating or editing blog posts within the **Categories** section. An attacker can inject a malicious JavaScript payload into the **Categories** content, which is then stored server-side.\n\nThis stored payload is later rendered unsafely when the **Categories** are viewed via blog posts, without proper output encoding, leading to stored cross-site scripting (XSS).\n\n### Affected Functionality\n- Blog post **Categories** creation functionality\n- Blog post **Categories** editing functionality\n- Blog post **Categories** storage and retrieval logic\n\n### Attack Scenario\n- An attacker creates or edits a blog post **Category** to include a malicious XSS payload in the category description or name.\n- The application stores this content without sanitization or encoding.\n- The payload persists and executes whenever the category is viewed within the blog posts section, leading to the execution of arbitrary JavaScript in the victim’s browser.\n\n### Impact\n- Persistent Stored XSS\n- Execution of arbitrary JavaScript in victims’ browsers\n- Privilege escalation when viewed by administrators or privileged users within the **Categories** functionality\n- Full administrator account takeover through **Categories** access\n- Full account takeover across all roles via **Categories** pages\n- Full compromise of the entire application via XSS in **Categories**\n\n**Endpoints:**\n- `/backend/blogs/create` (Categories specific)\n- `/backend/blogs/` (Categories view)\n- `/blog/{id}` (Rendered blog post under Categories)\n\n## Steps To Reproduce (POC)\n1. Go to the **Categories** section of the blog management panel.\n2. Create a new category or edit an existing category.\n3. Insert an XSS payload into the category content, such as:\n`<img src=x onerror=alert(document.domain)>`\n4. Save or publish the Categories.\n5. View the category via the blog posts in the administrative panel or public blog page under the Categories section.\n6. Notice the XSS payload executing automatically when the Category is viewed in the Blog Posts.\n\n## Remediation\n\n- **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.\n\n- **Apply output encoding:** Implement HTML entity encoding on all user-controlled data before rendering it in the browser. This helps neutralize potentially malicious input.\n\n- **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.\n\n- **Enforce security headers and cookie attributes:**\n - **Content Security Policy (CSP):** Define and enforce a strict CSP to limit the execution of unauthorized scripts.\n - **HttpOnly flag:** Set the `HttpOnly` attribute on session cookies to prevent client-side script access.\n - **SameSite attribute:** Configure the `SameSite` cookie attribute to mitigate Cross-Site Request Forgery (CSRF) risks.\n - **Secure flag:** Ensure all cookies are transmitted only over HTTPS by enabling the `Secure` attribute.\n\n These measures collectively reduce the impact of XSS and help prevent escalation paths such as CSRF via XSS.\n\n# Ready Video POC:\nhttps://mega.nz/file/SAdVxK7b#kFW_sFOim_d_1AnVcpwvzOEV4MHv33LLooL4Xa_Ymgg",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "ci4-cms-erp/ci4ms"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.31.0.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.28.6.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/ci4-cms-erp/ci4ms/security/advisories/GHSA-r33w-c82v-x5v7"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34567"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/ci4-cms-erp/ci4ms"
}, {
"type" : "WEB",
"url" : "https://github.com/ci4-cms-erp/ci4ms/releases/tag/0.31.0.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-79" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-01T22:06:50Z",
"nvd_published_at" : "2026-04-01T22:16:20Z"
}
}