Skip to main content
CVE-2025-65840VulnerabilityPublished Updated

CVE-2025-65840: PublicCMS · n/a

Affects PublicCMSSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Dec 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubsanluan/PublicCMSpkg:github/sanluan/PublicCMSOther threatsAffected
  • =5.202506
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. Immediately monitor official PublicCMS channels for patches or security advisories addressing CVE-2025-65840 and apply updates as soon as they become available. 2. Implement strict anti-CSRF tokens in all forms and state-changing requests within the CMS, especially in the CkEditorAdminController. 3. Enforce same-site cookie attributes (SameSite=Lax or Strict) to reduce CSRF attack surface. 4. Configure web application firewalls (WAFs) to detect and block suspicious CSRF patterns or unexpected POST requests targeting administrative endpoints. 5. Disable or restrict access to the CkEditorAdminController if it is not essential for daily operations. 6. Educate users and administrators about phishing and social engineering risks that could trigger CSRF attacks. 7. Conduct regular security audits and penetration testing focusing on CSRF and other web vulnerabilities. 8. Employ Content Security Policy (CSP) headers to restrict the sources of executable scripts and reduce the risk of malicious payload execution. 9. Review and tighten user session management and authentication mechanisms to limit the impact of compromised sessions. 10. Maintain comprehensive logging and monitoring to detect anomalous activities indicative of exploitation attempts.

Description

PublicCMS V5.202506.b is vulnerable to Cross Site Request Forgery (CSRF) in the CkEditorAdminController.

References

Community reviews

Loading reviews…