CVE-2026-34561: CI4MS Cross-Site Scripting Vulnerability

CRITICAL
Advisory Identifier: GHSA-gcfj-cf7j-vwgj
CVSS 9.1
CWE-79
Published
Advisory Summary

CVE-2026-34561 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 system settings (social media management) full platform compromise & 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-34561 at a Glance

CVE Identifier CVE-2026-34561
GHSA Identifier GHSA-gcfj-cf7j-vwgj
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product CI4MS
Package Ecosystem Packagist
Published Date
Last Updated

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:H/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-34561

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.

ci4-cms-erp/ci4ms fixed: 0.31.0.0
Upgrade ci4-cms-erp/ci4ms to 0.31.0.0
Verify Direct and Transitive Dependencies

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-34561, 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

## Summary ### **Vulnerability: Stored DOM XSS via System Settings – Social Media Management (Same-Page Attribute Breakout & Persistent Payload Injection)** - Stored Cross-site Scripting via Unsanitized Social Media Configuration Fields with Immediate Same-Page Execution ### Description The application fails to properly sanitize user-controlled input within **System Settings – Social Media Management**. Multiple configuration fields, including **Social Media** and **Social Media Link**, accept attacker-controlled input that is stored server-side and later rendered without proper output encoding. Unlike typical stored XSS that executes on other pages (such as public-facing landing pages), this vulnerability executes directly on the same settings page. The injected payload breaks out of the input attribute context and is immediately interpreted by the browser, resulting in same-page DOM-based XSS. This represents a different functionality and a separate vulnerability class from public-facing landing page injection. ### Affected Functionality - System Settings – Social Media Management configuration - Same-page rendering of user-controlled input fields - DOM attribute injection within form inputs - Storage and retrieval of social media configuration values ### Attack Scenario - An attacker injects a malicious JavaScript payload into one or more Social Media Management fields. - The payload breaks out of the HTML attribute context. - The application stores and re-renders the payload without sanitization or encoding. - The payload executes immediately on the same settings page when rendered. - The script executes in the browser context of the authenticated user managing settings. ### Impact - Persistent Stored XSS - Immediate Same-Page DOM XSS execution - Execution of arbitrary JavaScript in victims’ browsers - Administrative privilege escalation - Full administrator account takeover - Full account takeover across all roles - Full compromise of the entire platform Endpoints: - `/backend/settings/` (Social Media Management) ## Steps To Reproduce (POC) 1. Navigate to System Settings -> Social Media Management 2. Insert the following XSS payload into any Social Media or Social Media Link field: `test"><img src=1 onerror=alert()>" class="form-control" placeholder="Name" required>` 3. Save the settings 4. Observe that the payload breaks out of the input attribute context 5. The XSS executes immediately on the same page ## 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/PBEFBCpJ#rGGxjnPN38qDtmJssAgIoLuStBcQaZFpR0J1bKAXApc

CVE-2026-34561 Affected CI4MS Versions

1 component(s)
Fixed Versions:
0.31.0.0
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-34561?
CVE-2026-34561 is a security vulnerability in CI4MS involving System Settings (Social Media Management) Full Platform Compromise & Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which CI4MS versions are affected?
Affected versions include releases prior to 0.31.0.0 across affected packages: ci4-cms-erp/ci4ms.
What version fixes CVE-2026-34561?
Upgrading to 0.31.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is ci4-cms-erp/ci4ms affected?
Yes, ci4-cms-erp/ci4ms is affected in releases prior to 0.31.0.0. Upgrade your dependency to 0.31.0.0 or later.
What is the CVSS score of CVE-2026-34561?
CVE-2026-34561 has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-34561?
CVE-2026-34561 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (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.).
How can I check Packagist dependencies for CVE-2026-34561?
Run the dependency tree command: 'inspect dependencies for ci4-cms-erp/ci4ms'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-gcfj-cf7j-vwgj",
  "modified" : "2026-04-27T16:26:10Z",
  "published" : "2026-04-01T22:02:34Z",
  "aliases" : [ "CVE-2026-34561" ],
  "summary" : "CI4MS: System Settings (Social Media Management) Full Platform Compromise & Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS",
  "details" : "## Summary\n### **Vulnerability: Stored DOM XSS via System Settings – Social Media Management (Same-Page Attribute Breakout & Persistent Payload Injection)**\n- Stored Cross-site Scripting via Unsanitized Social Media Configuration Fields with Immediate Same-Page Execution\n\n### Description\nThe application fails to properly sanitize user-controlled input within **System Settings – Social Media Management**. Multiple configuration fields, including **Social Media** and **Social Media Link**, accept attacker-controlled input that is stored server-side and later rendered without proper output encoding.\n\nUnlike typical stored XSS that executes on other pages (such as public-facing landing pages), this vulnerability executes directly on the same settings page. The injected payload breaks out of the input attribute context and is immediately interpreted by the browser, resulting in same-page DOM-based XSS.\n\nThis represents a different functionality and a separate vulnerability class from public-facing landing page injection.\n\n### Affected Functionality\n- System Settings – Social Media Management configuration\n- Same-page rendering of user-controlled input fields\n- DOM attribute injection within form inputs\n- Storage and retrieval of social media configuration values\n\n### Attack Scenario\n- An attacker injects a malicious JavaScript payload into one or more Social Media Management fields.\n- The payload breaks out of the HTML attribute context.\n- The application stores and re-renders the payload without sanitization or encoding.\n- The payload executes immediately on the same settings page when rendered.\n- The script executes in the browser context of the authenticated user managing settings.\n\n### Impact\n- Persistent Stored XSS\n- Immediate Same-Page DOM XSS execution\n- Execution of arbitrary JavaScript in victims’ browsers\n- Administrative privilege escalation\n- Full administrator account takeover\n- Full account takeover across all roles\n- Full compromise of the entire platform\n\nEndpoints:\n- `/backend/settings/` (Social Media Management)\n\n## Steps To Reproduce (POC)\n1. Navigate to System Settings -> Social Media Management\n2. Insert the following XSS payload into any Social Media or Social Media Link field:\n`test\"><img src=1 onerror=alert()>\" class=\"form-control\" placeholder=\"Name\" required>`\n3. Save the settings\n4. Observe that the payload breaks out of the input attribute context\n5. The XSS executes immediately on the same page\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/PBEFBCpJ#rGGxjnPN38qDtmJssAgIoLuStBcQaZFpR0J1bKAXApc",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "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-gcfj-cf7j-vwgj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34561"
  }, {
    "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:02:34Z",
    "nvd_published_at" : "2026-04-01T22:16:19Z"
  }
}