CVE-2026-34569

Vulnerability: Stored DOM XSS via Blog Category Title (Persistent Payload Injection)

• Stored Cross-Site Scripting via Unsanitized Blog Category Title in Blog Management

Description

The application fails to properly sanitize user-controlled input when creating or editing blog categories. An attacker can inject a malicious JavaScript payload into the category title field, which is then stored server-side.

This stored payload is later rendered unsafely across public-facing blog category pages, administrative interfaces, and blog post views without proper output encoding, leading to stored cross-site scripting (XSS).

Affected Functionality

• Blog category creation functionality
• Blog category editing functionality
• Blog category storage and retrieval logic

Attack Scenario

• An attacker creates or edits a blog category title to include a malicious XSS payload.
• The application stores this value without sanitization or encoding.
• The payload persists and executes whenever the category title is rendered in affected views.

Steps To Reproduce (POC)

1. Go to the Blog Categories management page
2. Create or edit a category and insert an XSS payload into the category title such as:
   <img src=x onerror=alert(document.domain)>
3. Save the category
4. View a public blog category page, blog post page, or the administrative interface
5. Notice the XSS payload executing automatically

Ready Video POC:

https://mega.nz/file/GAFC3AJY#3LHyuyl7I7921UEeA-JlUYdckh6zGLCTy-6w9BNzSmQ

• Persistent Stored XSS
• Execution of arbitrary JavaScript in victims’ browsers
• Privilege escalation when viewed by administrators or privileged users
• Full administrator account takeover
• Full account takeover across all roles
• Full compromise of the entire application

Endpoints:

• /backend/blogs/categories/
• /blog/{id}

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-34569 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.31.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

• 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.

1. What is CVE-2026-34569? CVE-2026-34569 is a critical-severity cross-site scripting (XSS) vulnerability in ci4-cms-erp/ci4ms (composer), affecting versions <= 0.28.6.0. It is fixed in 0.31.0.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-34569? CVE-2026-34569 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of ci4-cms-erp/ci4ms are affected by CVE-2026-34569? ci4-cms-erp/ci4ms (composer) versions <= 0.28.6.0 is affected.
4. Is there a fix for CVE-2026-34569? Yes. CVE-2026-34569 is fixed in 0.31.0.0. Upgrade to this version or later.
5. Is CVE-2026-34569 exploitable, and should I be worried? Whether CVE-2026-34569 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-34569 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-34569? Upgrade ci4-cms-erp/ci4ms to 0.31.0.0 or later.