Skip to main content
VulnerabilityPublished Updated

CVE-2024-40543: PublicCMS · Server-Side Request Forgery (SSRF)

Affects PublicCMSSource CVE Database V5

0

Not known to be exploited · CVSS 6.4 Medium.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jul 2024

  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
GitHubsanluan/PublicCMSpkg:github/sanluan/PublicCMSOther threatsAffected
  • =4.0.202302
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 access to the /admin/ueditor endpoint to trusted administrative IP addresses or VPNs to reduce exposure.
  2. Implement strict input validation and URL whitelisting on the catchimage parameter to prevent requests to internal or sensitive network addresses.
  3. Employ network segmentation and firewall rules to limit the server’s ability to make outbound HTTP requests to internal services that should not be accessible.
  4. Monitor server logs for unusual outbound requests originating from the vulnerable endpoint to detect potential exploitation attempts.
  5. Use Web Application Firewalls (WAFs) with rules designed to detect and block SSRF patterns targeting the catchimage functionality.
  6. Regularly audit and rotate administrative credentials to reduce risk from compromised accounts.
  7. Stay alert for official patches or updates from PublicCMS and apply them promptly once available.
  8. Consider disabling or restricting the image capture feature if it is not essential to reduce the attack surface.
  9. Conduct internal penetration testing to identify if the vulnerability can be exploited in your environment and validate mitigations.
  10. Educate administrators about the risks of SSRF and the importance of secure configuration and credential management.

Description

PublicCMS v4.0.202302.e was discovered to contain a Server-Side Request Forgery (SSRF) via the component /admin/ueditor?action=catchimage.

References

Community reviews

Loading reviews…