Skip to main content
VulnerabilityPublished Updated

CVE-2025-63678: CMSMS · An Authenticated Arbitrary File Upload

Affects CMSMSSource CVE Database V5

0

Not known to be exploited · CVSS 3.8 Low.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
3.8Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2025

  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

Affected software

ProductAffectedFixed in
GitHubkasiasok/CMSMSpkg:github/kasiasok/CMSMSOther threatsAffected
  • =2.2.22
Fixed in–

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

AI-suggested

  1. Restrict administrator access strictly to trusted personnel and enforce strong, unique credentials with multi-factor authentication (MFA).
  2. Monitor and audit administrator activities and file upload endpoints for unusual or unauthorized uploads.
  3. Implement file upload validation and filtering at the web server or application firewall level to block executable file types such as PHP.
  4. Isolate the upload directory with strict permissions and disable execution rights on uploaded files to prevent code execution.
  5. Regularly review and update CMS and plugin versions; apply patches promptly once available.
  6. Employ network segmentation to limit the impact of a compromised CMS server.
  7. Conduct regular security assessments and penetration tests focusing on file upload functionalities.
  8. Educate administrators on the risks of file uploads and secure handling practices.
  9. Consider deploying runtime application self-protection (RASP) or web application firewalls (WAF) with rules targeting suspicious upload behavior.
  10. Maintain comprehensive backups to enable recovery in case of compromise.

Description

An authenticated arbitrary file upload vulnerability in the /uploads/ endpoint of CMS Made Simple Foundation File Manager v2.2.22 allows attackers with Administrator privileges to execute arbitrary code via uploading a crafted PHP file.

References

Community reviews

Loading reviews…