CVE-2026-34989
Stored XSS in CI4MS profile name before 31.0.0.0.
Is CVE-2026-34989 being exploited?
Not confirmed. CVE-2026-34989 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-34989?
CVE-2026-34989 is rated Critical with a CVSS score of 9.4. 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-34989?
Yes. A fix has been recorded for CVE-2026-34989. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-34989 affect?
CVE-2026-34989 affects CI4MS (CodeIgniter 4-based CMS skeleton), CodeIgniter 4 CMS skeleton. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-34989?
Upgrade to 31.0.0.0+ to fix stored XSS
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored XSS via profile name; attacker can run scripts in victims' browsers, potentially steal sessions and deface content.
Immediate action required
- affected< 31.0.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.