CI4MS is a CodeIgniter 4-based content management system skeleton. Prior to version 0.31.9.0, the custom html_purify validation rule used to sanitize blog post bodies relies on by-reference mutation (?string &$str), but CodeIgniter 4's validator passes a local copy of the value, so the sanitized text is silently discarded. The Blog controller writes $lanData['content'] directly into blog_langs.content, and the public template echoes it without escaping — yielding stored XSS executable in any visitor's browser, including the superadmin when previewing or editing posts. Version 0.31.9.0 patches the issue.
CVE-2026-45138
This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(medium)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 4.3%
- KEV
- Not listed
Published
May 18, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 19, 2026v0.31.9.0 — Security Hardening & Patch Release
Patch available: ci4-cms-erp/ci4ms 0.31.9.0
https://github.com/ci4-cms-erp/ci4ms/releases/tag/0.31.9.0Stored XSS in Blog Content via Broken `html_purify` Validation Rule · Advisory · ci4-cms-erp/ci4ms · GitHub
https://github.com/ci4-cms-erp/ci4ms/security/advisories/GHSA-2m69-jmvh-6chrVendor Advisories for CVE-2026-45138(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ci4-cms-erp/ci4ms | 0.21.0 ... 0.31.9 (57 versions) | 0.31.9.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:16 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-24 06:17 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-45138?
When was CVE-2026-45138 disclosed?
Is CVE-2026-45138 actively exploited?
What is the CVSS score of CVE-2026-45138?
How do I remediate CVE-2026-45138?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45138
Is Your Infrastructure Affected by CVE-2026-45138?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.