CVE-2018-9134: CSRF
First published: Fri Mar 30 2018(Updated: )
file_manage_control.php in DedeCMS 5.7 has CSRF in an fmdo=rename action, as demonstrated by renaming an arbitrary file under uploads/userup to a .php file under the web root to achieve PHP code execution. This uses the oldfilename and newfilename parameters.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Dedecms v6 | =5.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-9134?
CVE-2018-9134 is considered a critical vulnerability due to the potential for remote PHP code execution.
How do I fix CVE-2018-9134?
To mitigate CVE-2018-9134, you should upgrade DedeCMS to a patched version that fixes the CSRF vulnerability.
What type of vulnerability is CVE-2018-9134?
CVE-2018-9134 is a Cross-Site Request Forgery (CSRF) vulnerability affecting DedeCMS.
Which versions of DedeCMS are affected by CVE-2018-9134?
CVE-2018-9134 specifically affects DedeCMS version 5.7.
What exploit can occur due to CVE-2018-9134?
CVE-2018-9134 allows an attacker to rename files, potentially executing arbitrary PHP code on the server.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/weakness
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/dedecms
- canonical/dedecms v6
- version/dedecms v6/5.7