CVE-2024-28675: cms · n/a
Affects cmsSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 08:30 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHub777erp/cmspkg:github/777erp/cmsOther threats | Affected
| 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-28675, organizations should immediately implement the following measures: 1) Restrict access to the /dede/diy_edit.php endpoint using web application firewalls (WAFs) or IP whitelisting to limit exposure. 2) Implement or verify the presence of anti-CSRF tokens in all state-changing requests within DedeCMS, ensuring that requests without valid tokens are rejected. 3) Educate users and administrators about the risks of CSRF and the importance of avoiding clicking on suspicious links or visiting untrusted websites while authenticated. 4) Monitor web server and application logs for unusual or unauthorized requests targeting the vulnerable endpoint. 5) If possible, temporarily disable or restrict the functionality of the vulnerable module until an official patch is released. 6) Keep abreast of updates from DedeCMS developers and apply patches promptly once available. 7) Employ multi-factor authentication (MFA) to reduce the risk of account compromise that could be leveraged in conjunction with CSRF attacks. 8) Conduct regular security assessments and penetration testing focused on CSRF and related web vulnerabilities to identify and remediate weaknesses proactively.
Description
DedeCMS v5.7 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /dede/diy_edit.php