Skip to main content
VulnerabilityPublished Updated

CVE-2024-28431: 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, 14:05 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 26% 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
GitHubitsqian797/cmspkg:github/itsqian797/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

  1. Immediately restrict access to the /dede/catalog_del.php endpoint using web application firewalls (WAF) or access control lists (ACLs) to limit exposure.
  2. Implement CSRF tokens in all forms and state-changing requests within DedeCMS to ensure requests are legitimate and originate from authorized users.
  3. Educate users and administrators about the risks of clicking untrusted links or visiting suspicious websites while authenticated.
  4. Monitor web server logs and CMS activity for unusual or unauthorized catalog deletion attempts.
  5. If possible, isolate administrative interfaces to trusted networks or VPNs to reduce exposure.
  6. Regularly back up website data and configurations to enable recovery in case of data loss.
  7. Stay alert for official patches or updates from DedeCMS developers and apply them promptly once available.
  8. Consider deploying Content Security Policy (CSP) headers to reduce the risk of malicious script execution that could facilitate CSRF attacks.

Description

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

References

Community reviews

Loading reviews…