Skip to main content
VulnerabilityPublished Updated

CVE-2024-27689: cms · Cross-Site Request Forgery (CSRF)

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% 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 Mar 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
GitHubxin246/cmspkg:github/xin246/cmsOther threatsAffected
  • =1.2.4
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-27689, organizations should implement the following specific measures: 1) Apply CSRF tokens to all state-changing requests, especially the /update-article.php endpoint, ensuring that each request includes a unique, unpredictable token validated server-side. 2) Enforce SameSite cookie attributes to restrict cross-origin requests. 3) Implement strict referer header validation to confirm requests originate from trusted sources. 4) Educate users about the risks of clicking untrusted links and encourage use of updated browsers with anti-CSRF protections. 5) Monitor web server logs for unusual POST requests or patterns indicative of CSRF attempts. 6) If possible, restrict access to the CMS backend by IP whitelisting or VPN requirements to reduce exposure. 7) Regularly review and update CMS software and apply patches once available. 8) Consider deploying a web application firewall (WAF) with rules to detect and block CSRF attack patterns. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable endpoint and practical controls to reduce attack surface.

Description

Stupid Simple CMS v1.2.4 was discovered to contain a Cross-Site Request Forgery (CSRF) via /update-article.php.

References

Community reviews

Loading reviews…