CVE-2024-30855: cms · n/a
Affects cmsSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% 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 29 Dec 2025
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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHublimingqian123/cmspkg:github/limingqian123/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-30855, organizations should first verify if they are running DedeCMS version 5.7 and restrict access to the /src/dede/makehtml_list_action.php endpoint. Implementing anti-CSRF tokens in all state-changing requests is critical to prevent unauthorized actions. Web application firewalls (WAFs) can be configured to detect and block suspicious CSRF patterns or unusual POST requests targeting this endpoint. User sessions should be validated rigorously, including checking the Referer header and enforcing same-site cookies to reduce CSRF attack surface. Organizations should educate users about the risks of clicking on untrusted links while authenticated. Monitoring web server logs for unusual activity related to the vulnerable script can provide early detection of exploitation attempts. If patches become available, immediate application is essential. In the absence of official patches, consider isolating or disabling vulnerable functionality temporarily. Regular security assessments and penetration testing focused on CSRF vulnerabilities will help maintain a secure posture.
Description
DedeCMS v5.7 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /src/dede/makehtml_list_action.php.