dbcve.org
DedecmsApplication

CVE-2018-9134

HIGH · 8.8 CVSS v3.0 Published 2018-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DedeCMS 5.7 file_manage_control.php lacks anti-CSRF protection on the fmdo=rename action. Attackers can trick authenticated administrators into submitting malicious requests via crafted pages, allowing renaming of files from uploads/userup to .php files in the web root, achieving arbitrary PHP code execution.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all admin actions including file operations, require POST requests with token validation, and validate file rename operations to prevent path traversal and extension changes to executable types.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DedecmsApplication
Affected:= 5.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm DedeCMS installation and version
    Locate the version file in the DedeCMS installation, typically found in /data/admin/ver.txt or by checking the login page source for version strings. Access the administrator login at /dede/login.php or /admin/login.php.
    Affected if The installed version is DedeCMS 5.7 exactly.
  2. Locate the vulnerable file
    Check for the presence of file_manage_control.php in the admin directory, typically found at /dede/file_manage_control.php or /admin/file_manage_control.php.
    Affected if The file exists in the admin directory.
  3. Check if rename action lacks CSRF protection
    Open file_manage_control.php and search for the rename handling code (fmdo=rename). Examine whether a token validation check exists before processing the rename operation. Look for token/session validation functions like token_check, csrf_check, or similar in the rename action block.
    Affected if The rename action block contains no token validation or CSRF check logic.
  4. Verify admin access to file management
    Log into the DedeCMS admin panel and navigate to the file manager module. Check if an authenticated administrator can access the file rename functionality.
    Affected if The file manager is accessible to authenticated administrators without additional CSRF protection on rename operations.
  5. Check uploads directory configuration
    Examine the uploads/userup directory permissions and configuration. Verify if the web server has write access to this directory.
    Affected if The uploads/userup directory exists and is writable by the web server.

A user is affected if running DedeCMS 5.7 with file_manage_control.php present and the rename action lacks anti-CSRF token validation, allowing authenticated admin sessions to be exploited via malicious crafted pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all admin actions including file operations, require POST requests with token validation, and validate file rename operations to prevent path traversal and extension changes to executable types.

Fix this in Dedecms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-9134 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-9134 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data