CVE-2026-41201
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. In version 0.31.4.0, an attacker can achieve Full Account Takeover & Privilege Escalation via Stored DOM XSS in backup module filename field manipulated via a sql file that tampers with the file name field to contain hidden XSS payload. This issue has been patched in version 0.31.5.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCI4MS version 0.31.4.0 contains a stored DOM XSS vulnerability in the backup module's filename field. Attackers can tamper with SQL backup files to inject malicious XSS payloads into the filename, which executes when viewed by administrators, enabling full account takeover and privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify CI4MS versionLocate and verify the installed CI4MS version number, typically accessible via the admin about page, version manifest file, or system info endpoint. Compare your version against the affected range.Affected if Installed version is 0.31.4.0 (the vulnerable version) or between 0.31.4.0 and 0.31.5.0 if earlier versions share the flaw
-
Confirm backup module is enabledVerify that the backup module is active and accessible in your CI4MS installation. Check the admin panel navigation or module configuration to confirm the backup feature is present and not disabled.Affected if The backup module is enabled and users have the ability to create, upload, or manage SQL backup files
-
Inspect existing backup filenamesReview all stored SQL backup files in the system. Examine the filename field for each backup entry visible in the backup management interface. Look for any unexpected characters or patterns that may indicate injection.Affected if Any backup file in the system contains a filename with unsanitized input, particularly HTML tags, script keywords, or event handlers like onload or onerror
-
Check admin logs for XSS indicatorsReview administrator access logs and audit trails for the backup module. Look for evidence of script execution, unusual browser console activity, or unexpected requests containing XSS payloads when backup files were viewed.Affected if Logs show XSS execution attempts or successful payload delivery in the context of backup filename viewing
You are affected if running CI4MS version 0.31.4.0 with the backup module enabled and any backup files contain unsanitized filename data that could execute as JavaScript when viewed by an administrator.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to version 0.31.5.0 which contains the patch. If immediate patching is not possible, disable the backup module and implement strict input validation/sanitization on all filename fields parsed from SQL backup files.
CI4MS version 0.31.5.0
- Backup the current CI4MS installation and database before proceeding with the upgrade
- Download CI4MS version 0.31.5.0 from the official repository
- Replace the existing installation files with the new version 0.31.5.0 files
- Migrate any custom configurations from the backup to the new installation
- Verify the backup module functionality works correctly in the updated version
- Confirm the XSS vulnerability in the backup module filename field is resolved by testing with a benign test payload
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41201 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data