dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-41202

CRITICAL · 9.4 CVSS v4.0 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. Prior to version 0.31.5.0, ci4ms Backup::restore extracts user uploaded ZIP archives without validating entry names, allowing an authenticated backend user with the backup create permission to write files to arbitrary filesystem locations (Zip Slip) and achieve remote code execution by dropping a PHP file under the public web root. 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 · high confidence

CI4MS Backup::restore function lacks path traversal validation on ZIP archive entries, allowing authenticated users with backup permissions to extract files to arbitrary filesystem locations (Zip Slip). By crafting a malicious ZIP with entries like ../../../public/shell.php, attackers can achieve remote code execution.

MitigationUpgrade to CI4MS version 0.31.5.0 or later which implements proper path validation on ZIP entries before extraction. Until patched, revoke backup/restore permissions from untrusted users.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CI4MS installation
    Locate CI4MS backup system files in the environment - check for backup-related modules, libraries, or plugins that implement Backup::restore functionality
    Affected if CI4MS Backup::restore function is present in the environment
  2. Determine installed version
    Find and read the version file or metadata for the CI4MS installation using standard version lookup methods for the product
    Affected if The installed version is lower than 0.31.5.0 or the version cannot be determined
  3. Verify backup restore function is accessible
    Check if the Backup::restore function is exposed and enabled - confirm the restore operation is callable through the web interface or API
    Affected if The Backup::restore function is accessible without additional safeguards
  4. Confirm authenticated user permissions
    Audit user accounts and roles to determine if any authenticated backend users possess backup create permission
    Affected if Authenticated users with backup create permission exist in the system
  5. Check for recent restore operations
    Review backup logs, access logs, or file modification timestamps in common web root directories for signs of recent restore operations
    Affected if Restore operations have been performed and files were extracted to locations outside the intended backup directory

The environment is affected if CI4MS with Backup::restore is installed, the version is below 0.31.5.0, and authenticated users with backup create permission can access the restore function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to CI4MS version 0.31.5.0 or later which implements proper path validation on ZIP entries before extraction. Until patched, revoke backup/restore permissions from untrusted users.

Recommended fix High confidence

0.31.5.0

  1. Backup the current CI4MS installation and database before proceeding
  2. Update CI4MS to version 0.31.5.0 or later by running 'composer update' if using Composer, or by downloading the latest release from the official repository
  3. Verify the Backup::restore function now properly validates ZIP entry names before extraction
  4. Confirm the update was successful by checking the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41202 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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