CVE-2024-29684: cms · Cross-Site Request Forgery (CSRF)
Affects cmsSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 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 |
|---|---|---|
GitHubiimiss/cmspkg:github/iimiss/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
Given the lack of an official patch at this time, organizations should take immediate practical steps to mitigate the risk: 1) Restrict access to the vulnerable /src/dede/makehtml_homepage.php endpoint using web application firewalls (WAFs) or access control lists to block unauthorized requests. 2) Implement CSRF protections such as verifying origin headers or requiring anti-CSRF tokens for sensitive operations if possible. 3) Monitor web server logs for suspicious requests targeting the vulnerable script and unusual POST requests that could indicate exploitation attempts. 4) Isolate or sandbox the affected CMS environment to limit potential damage in case of compromise. 5) Regularly back up website data and configurations to enable rapid recovery. 6) Stay alert for vendor updates or security advisories providing patches or official fixes and apply them immediately upon release. 7) Educate administrators and developers about this vulnerability to avoid unsafe customizations that could exacerbate risk. 8) Consider migrating to alternative CMS platforms if timely patches are not forthcoming and risk remains high.
Description
DedeCMS v5.7 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /src/dede/makehtml_homepage.php allowing a remote attacker to execute arbitrary code.