GHSA-FHRF-Q333-82FM
Vulnerability from github – Published: 2026-04-01 22:07 – Updated: 2026-04-06 17:14Summary
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.
Impact
- 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}
Steps To Reproduce (POC)
- Go to the Blog Categories management page
- Create or edit a category and insert an XSS payload into the category title such as:
<img src=x onerror=alert(document.domain)> - Save the category
- View a public blog category page, blog post page, or the administrative interface
- Notice the XSS payload executing automatically
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
HttpOnlyattribute on session cookies to prevent client-side script access. - SameSite attribute: Configure the
SameSitecookie attribute to mitigate Cross-Site Request Forgery (CSRF) risks. - Secure flag: Ensure all cookies are transmitted only over HTTPS by enabling the
Secureattribute.
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/GAFC3AJY#3LHyuyl7I7921UEeA-JlUYdckh6zGLCTy-6w9BNzSmQ
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.28.6.0"
},
"package": {
"ecosystem": "Packagist",
"name": "ci4-cms-erp/ci4ms"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.31.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-34569"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-01T22:07:37Z",
"nvd_published_at": "2026-04-01T22:16:20Z",
"severity": "CRITICAL"
},
"details": "## Summary\n### **Vulnerability: Stored DOM XSS via Blog Category Title (Persistent Payload Injection)**\n- Stored Cross-Site Scripting via Unsanitized Blog Category Title in Blog Management\n\n### Description\nThe 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.\n\nThis 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).\n\n### Affected Functionality\n- Blog category creation functionality\n- Blog category editing functionality\n- Blog category storage and retrieval logic\n\n### Attack Scenario\n- An attacker creates or edits a blog category title to include a malicious XSS payload.\n- The application stores this value without sanitization or encoding.\n- The payload persists and executes whenever the category title is rendered in affected views.\n\n### Impact\n- Persistent Stored XSS\n- Execution of arbitrary JavaScript in victims\u2019 browsers\n- Privilege escalation when viewed by administrators or privileged users\n- Full administrator account takeover\n- Full account takeover across all roles\n- Full compromise of the entire application\n\nEndpoints:\n- `/backend/blogs/categories/`\n- `/blog/{id}`\n\n## Steps To Reproduce (POC)\n1. Go to the Blog Categories management page\n2. Create or edit a category and insert an XSS payload into the category title such as:\n`\u003cimg src=x onerror=alert(document.domain)\u003e`\n3. Save the category\n4. View a public blog category page, blog post page, or the administrative interface\n5. Notice the XSS payload executing automatically\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/GAFC3AJY#3LHyuyl7I7921UEeA-JlUYdckh6zGLCTy-6w9BNzSmQ",
"id": "GHSA-fhrf-q333-82fm",
"modified": "2026-04-06T17:14:44Z",
"published": "2026-04-01T22:07:37Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/ci4-cms-erp/ci4ms/security/advisories/GHSA-fhrf-q333-82fm"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34569"
},
{
"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"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "CI4MS: Blogs Categories Full Account Takeover for All-Roles \u0026 Privilege-Escalation via Stored DOM XSS"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.