https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 17 Oct 2026 06:58:50 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-278729 EUVD-2026-278729 https://cve.radiocsirt.org/vuln/euvd-2026-278729 https://cve.radiocsirt.org/vuln/fkie_cve-2026-34568 <p>CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. Prior to version 0.31.0.0, the application fails to properly sanitize user-controlled input when creating or editing blog posts. An attacker can inject a malicious JavaScript payload into blog post content, which is then stored server-side. This stored payload is later rendered unsafely in multiple application views without proper output encoding, leading to stored cross-site scripting (XSS). This issue has been patched in version 0.31.0.0.</p> <p>CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. Prior to version 0.31.0.0, the application fails to properly sanitize user-controlled input when creating or editing blog posts. An attacker can inject a malicious JavaScript payload into blog post content, which is then stored server-side. This stored payload is later rendered unsafely in multiple application views without proper output encoding, leading to stored cross-site scripting (XSS). This issue has been patched in version 0.31.0.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-34568 https://cve.radiocsirt.org/vuln/ghsa-x7wh-g25g-53vg <p><strong>Affected:</strong> Packagist: ci4-cms-erp/ci4ms</p> <p>## Summary ### **Vulnerability: Stored DOM XSS via Blog Post Content (Persistent Payload Injection)** - Stored Cross-Site Scripting via Unsanitized Blog Post Content in Blog Management</p> <p>### Description The application fails to properly sanitize user-controlled input when creating or editing blog posts. An attacker can inject a malicious JavaScript payload into blog post content, which is then stored server-side.</p> <p>This stored payload is later rendered unsafely in multiple application views without proper output encoding, leading to stored cross-site scripting (XSS).</p> <p>### Affected Functionality - Blog post creation functionality - Blog post editing functionality - Blog post storage and retrieval logic</p> <p>### Attack Scenario - An attacker creates or edits a blog post to include a malicious XSS payload. - The application stores this content without sanitization or encoding. - The payload persists and executes whenever the blog post is rendered in affected views.</p> <p>### 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</p> <p>Endpoints: - `/backend/blogs/create` - `/backend/blogs/` - `/blog/{id}`</p> <p>## Steps To Reproduce (POC) 1. Go to the Blog Post Create or Edit page 2. Insert an XSS payload into the blog post content such as: `&lt;img src=x onerror=alert(documen…</p> <p><strong>Affected:</strong> Packagist: ci4-cms-erp/ci4ms</p> <p>## Summary ### **Vulnerability: Stored DOM XSS via Blog Post Content (Persistent Payload Injection)** - Stored Cross-Site Scripting via Unsanitized Blog Post Content in Blog Management</p> <p>### Description The application fails to properly sanitize user-controlled input when creating or editing blog posts. An attacker can inject a malicious JavaScript payload into blog post content, which is then stored server-side.</p> <p>This stored payload is later rendered unsafely in multiple application views without proper output encoding, leading to stored cross-site scripting (XSS).</p> <p>### Affected Functionality - Blog post creation functionality - Blog post editing functionality - Blog post storage and retrieval logic</p> <p>### Attack Scenario - An attacker creates or edits a blog post to include a malicious XSS payload. - The application stores this content without sanitization or encoding. - The payload persists and executes whenever the blog post is rendered in affected views.</p> <p>### 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</p> <p>Endpoints: - `/backend/blogs/create` - `/backend/blogs/` - `/blog/{id}`</p> <p>## Steps To Reproduce (POC) 1. Go to the Blog Post Create or Edit page 2. Insert an XSS payload into the blog post content such as: `&lt;img src=x onerror=alert(documen…</p> https://cve.radiocsirt.org/vuln/ghsa-x7wh-g25g-53vg