Skip to main content
VulnerabilityPublished Updated

CVE-2024-28673: 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 30% 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-28673, organizations should implement the following specific measures: 1) Apply any available patches or updates from DedeCMS developers as soon as they are released. 2) If patches are unavailable, implement manual CSRF protections by adding anti-CSRF tokens to all state-changing requests, especially those targeting /dede/mychannel_edit.php. 3) Enforce strict referer or origin header validation to ensure requests originate from trusted sources. 4) Limit the exposure of the vulnerable endpoint by restricting access to trusted IP addresses or authenticated users only. 5) Educate users about the risks of clicking on untrusted links or visiting suspicious websites while authenticated to the CMS. 6) Monitor web server logs and application behavior for unusual or unauthorized requests targeting the vulnerable endpoint. 7) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block CSRF attack patterns. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable endpoint and the nature of the CSRF attack vector.

Description

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

References

Community reviews

Loading reviews…