CVE-2026-34559
Stored XSS in CI4MS blog tag creation (pre-0.31.0.0).
Is CVE-2026-34559 being exploited?
Not confirmed. CVE-2026-34559 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-34559?
CVE-2026-34559 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-34559?
Yes. A fix has been recorded for CVE-2026-34559. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-34559 affect?
CVE-2026-34559 affects CI4MS (CodeIgniter 4-based CMS skeleton) pre-0.31.0.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-34559?
Upgrade to 0.31.0.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored XSS: attacker-supplied tag name stored server-side and executed on public and admin pages.
Patch when possible
- affected< 0.31.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.