Skip to main content
VulnerabilityPublished Updated

CVE-2024-28665: 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 25% 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 13 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
GitHub777erp/cmspkg:github/777erp/cmsOther threatsAffected
  • =5.7
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-28665, organizations should implement the following specific measures: 1) Apply any available patches or updates from the DedeCMS vendor as soon as they are released. 2) If patches are not yet available, implement anti-CSRF tokens in all forms and state-changing requests, especially in /dede/article_add.php. 3) Enforce strict referer header validation to ensure requests originate from trusted sources. 4) Limit user privileges to the minimum necessary, reducing the number of users who can perform article additions or modifications. 5) Educate users about phishing and social engineering attacks that could trick them into submitting malicious requests. 6) Monitor web server logs and CMS activity for unusual or unauthorized content changes. 7) Consider deploying Web Application Firewalls (WAFs) with rules to detect and block CSRF attack patterns targeting DedeCMS. 8) Regularly review and audit CMS configurations and access controls to minimize exposure.

Description

DedeCMS v5.7 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via the component /dede/article_add.php

References

Community reviews

Loading reviews…