CriticalPublic exploit

Stored XSS in CI4MS blog post creation/editing

IdentifiersCVE-2026-34568CWE-79· Improper Neutralization of Input…

CVE-2026-34568 is a stored cross-site scripting vulnerability in CI4MS, a CodeIgniter 4-based CMS skeleton. In versions prior to 0.31.0.0, user-controlled input supplied during blog post creation or editing is not properly sanitized, and the resulting content is later rendered in multiple application views without proper output encoding. This allows malicious JavaScript embedded in blog post content to be stored server-side and executed when the affected content is displayed.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows persistent execution of attacker-controlled JavaScript in the context of the CI4MS application when affected blog content is rendered. Because the payload is stored server-side and reused across views, the issue can affect multiple users who access the malicious post content. The provided CVSS context indicates potential high confidentiality impact, with additional integrity and availability impact, consistent with session theft, unauthorized actions in the victim's browser, content manipulation, and other browser-based compromise effects under the application's origin.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict or disable untrusted users' ability to create or edit blog posts, especially in roles with content publishing permissions. Apply strict output encoding to all blog content rendering paths, review templates and views for unsafe raw rendering, and consider deploying a restrictive Content Security Policy to reduce the impact of injected script execution. Validate and sanitize rich-text or HTML-capable fields consistently before storage and before display.

Remediation

Patch, then assume compromise.

Upgrade CI4MS to version 0.31.0.0 or later, which contains the patch for this issue. Ensure that blog post content handling applies both appropriate server-side sanitization for untrusted input and context-appropriate output encoding in every view that renders stored content.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Ci4-Cms-ErpCi4msapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

7 SOURCESView more in app

cvefeed high severityNews

Apr 1, 2026

CVE-2026-34568 - CI4MS: Blogs Posts Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS

A stored cross-site scripting vulnerability in CI4MS prior to version 0.31.0.0 caused by improper sanitization of blog post input and unsafe rendering of stored content.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6