CVE-2024-42523: publiccms · Unrestricted File Upload
Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
AI-suggested
Organizations should immediately audit and restrict access to the publiccms administrative interface to trusted personnel only, enforcing strong authentication and access controls. Implement multi-factor authentication to reduce the risk of credential compromise. Monitor and log all file upload activities on the cmsTemplate/saveMetaData endpoint to detect anomalous behavior. If possible, disable or restrict file upload functionality in the affected endpoint until a vendor patch or update is available. Employ web application firewalls (WAFs) with rules to detect and block suspicious file uploads or payloads. Regularly update publiccms to the latest version once patches addressing this vulnerability are released. Conduct thorough security assessments and penetration testing focusing on file upload functionalities. Additionally, implement network segmentation to limit the impact of potential compromises and maintain offline backups to enable recovery from attacks.
Description
publiccms V4.0.202302.e and before is vulnerable to Any File Upload via publiccms/admin/cmsTemplate/saveMetaData