Skip to main content
VulnerabilityPublished Updated

CVE-2024-46410: PublicCMS · Cross-site Scripting

Affects PublicCMSSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 15:59 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Oct 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.202406
Fixed in–

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

AI-suggested

To mitigate CVE-2024-46410, organizations should implement strict input validation and output encoding in the Category Management feature of PublicCMS to prevent injection of malicious scripts. Employing a robust Content Security Policy (CSP) can help reduce the impact of potential XSS attacks by restricting script execution sources. Administrators should enforce the principle of least privilege, ensuring that only necessary users have access to category management functions. Regularly monitoring user activity and logs for suspicious behavior can help detect attempted exploitation. Since no official patches are currently available, organizations should consider temporary workarounds such as disabling or restricting access to the vulnerable feature until a fix is released. Keeping PublicCMS and all related components updated and subscribing to vendor security advisories is critical. Additionally, educating users about the risks of interacting with untrusted links or content within the CMS environment can reduce the likelihood of successful attacks.

Description

PublicCMS V4.0.202406.d was discovered to contain a cross-site scripting (XSS) vulnerability via a crafted script to the Category Managment feature

References

Community reviews

Loading reviews…