Skip to main content
VulnerabilityPublished

CVE-2026-25510: ci4-cms-erp ci4ms · Unrestricted File Upload

Affects ci4-cms-erp ci4msSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical : upgrade to 0.28.5.0 as a priority.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.28.5.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade ci4ms and ci4-cms-erp/ci4ms to 0.28.5.0.

Affected software

ProductAffectedFixed in
ci4-cms-erpci4msAffected
  • <0.28.5.0
Fixed in
  • 0.28.5.0
GitHubci4-cms-erp/ci4mspkg:github/ci4-cms-erp/ci4msOther threatsAffected
  • <0.28.5.0
Fixed in
  • 0.28.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade all ci4ms installations to version 0.28.5.0 or later, where the vulnerability is patched.
  2. Review and tighten RBAC policies to ensure that only trusted users have file editor permissions.
  3. Implement strict file upload validation and sanitization, restricting allowed file types to safe formats and blocking executable files such as PHP.
  4. Employ web application firewalls (WAFs) with rules to detect and block suspicious file upload attempts and execution patterns.
  5. Monitor logs for unusual file upload activities and unexpected PHP file creations in upload directories.
  6. Segment the network to isolate CMS administrative interfaces from the broader corporate network, limiting potential lateral movement.
  7. Conduct regular security audits and penetration tests focusing on file upload functionalities.
  8. Educate administrators and developers about secure file handling practices and the risks of excessive permissions.
  9. If immediate upgrade is not feasible, consider disabling file upload features temporarily or restricting access to the CMS backend via IP whitelisting or VPN.
  10. Maintain up-to-date backups and incident response plans to quickly recover from potential compromises.

Description

CVE-2026-25510 is a critical vulnerability in ci4ms, a CodeIgniter 4-based CMS, allowing authenticated users with file editor permissions to upload and execute arbitrary PHP code via unrestricted file uploads. This leads to Remote Code Execution (RCE) without user interaction. The flaw affects versions prior to 0.28.5.0 and has been patched in that release. Exploitation requires authentication but no additional user interaction. The vulnerability impacts confidentiality, integrity, and availability severely, with a CVSS score of 10. European organizations using ci4ms in their web infrastructure are at risk, especially those with exposed or poorly segmented administrative interfaces. Mitigation involves upgrading to version 0.

References

Community reviews

Loading reviews…