CVE-2024-28432: cms · Cross-Site Request Forgery (CSRF)
Affects cmsSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% 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 |
|---|---|---|
GitHubitsqian797/cmspkg:github/itsqian797/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-28432, organizations should first verify if they are running DedeCMS version 5.7 and prioritize upgrading to a patched version once available. In the absence of an official patch, immediate mitigations include implementing anti-CSRF tokens in all state-changing forms and requests, especially in /dede/article_edit.php. Enforcing strict referer header validation can help block unauthorized cross-origin requests. Web Application Firewalls (WAFs) should be configured to detect and block suspicious CSRF attack patterns targeting the CMS. User education is critical: train authenticated users to avoid clicking on untrusted links or visiting suspicious websites while logged into the CMS. Additionally, monitoring CMS logs for unusual activity or unauthorized content changes can provide early detection of exploitation attempts. Restricting access to the article editing interface by IP or VPN can reduce exposure. Finally, consider implementing multi-factor authentication (MFA) to reduce the risk of session hijacking that could facilitate CSRF attacks.
Description
DedeCMS v5.7 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via the component /dede/article_edit.php.