Skip to main content
VulnerabilityPublished

CVE-2025-12346: MaxSite CMS · Unrestricted Upload

Affects MaxSite CMSSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
MaxSite CMSAffected
  • =109
Fixed in–

AI-suggested

  1. Immediately restrict or disable the vulnerable HTTP Header Handler component or the specific file uploads-require-maxsite.php if feasible.
  2. Implement strict input validation and sanitization for HTTP headers, especially X-Requested-FileName and X-Requested-FileUpDir, to prevent manipulation.
  3. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious upload attempts targeting these headers.
  4. Monitor web server logs for unusual file upload activity or access patterns related to the vulnerable component.
  5. Isolate MaxSite CMS installations in segmented network zones to limit lateral movement if compromised.
  6. Regularly back up website data and configurations to enable rapid recovery.
  7. Consider migrating to alternative CMS platforms with active vendor support if patching is not forthcoming.
  8. Stay alert for any future patches or vendor advisories and apply updates promptly.
  9. Conduct penetration testing focused on file upload functionalities to identify residual risks.
  10. Educate web administrators about the risks of unrestricted file uploads and secure configuration best practices.

Description

A vulnerability was detected in MaxSite CMS up to 109. This vulnerability affects unknown code of the file application/maxsite/admin/plugins/auto_post/uploads-require-maxsite.php of the component HTTP Header Handler. Performing manipulation of the argument X-Requested-FileName/X-Requested-FileUpDir results in unrestricted upload. Remote exploitation of the attack is possible. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…