CVE-2024-30855
Cross-Site Request Forgery in DedeCMS v5.7 makehtml_list_action.php
Publication date: 2025-12-29
Last updated on: 2025-12-29
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dede | dedecms | 5.7 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Cross-Site Request Forgery (CSRF) issue in DedeCMS version 5.7, specifically in the /src/dede/makehtml_list_action.php file. It allows an attacker to trick a logged-in user into executing unwanted actions on the web application without their consent.
How can this vulnerability impact me? :
The CSRF vulnerability can allow attackers to perform unauthorized actions on behalf of authenticated users, potentially leading to unauthorized changes or operations within the DedeCMS application.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable script /src/dede/makehtml_list_action.php in DedeCMS version 5.7 installations. Since it is a CSRF vulnerability, monitoring for unauthorized or suspicious POST requests to this script could help detect exploitation attempts. Specific commands to detect the file include: `find /path/to/webroot -name makehtml_list_action.php` or using web server access logs to search for requests to this endpoint, e.g., `grep 'makehtml_list_action.php' /var/log/apache2/access.log`. However, no specific detection commands are provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to /src/dede/makehtml_list_action.php, implementing CSRF protection mechanisms such as tokens in forms, and ensuring that only authorized users can perform actions via this script. Additionally, monitoring and blocking suspicious requests targeting this endpoint can help reduce risk. Since no official patch or update is mentioned, applying web application firewall (WAF) rules to block CSRF attempts or disabling the vulnerable functionality temporarily are advisable. [1]