CVE-2017-17727
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 · uneditedDedeCMS through 5.6 allows arbitrary file upload and PHP code execution by embedding the PHP code in a .jpg file, which is used in the templet parameter to member/article_edit.php.
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 confidenceDedeCMS through version 5.6 has an arbitrary file upload vulnerability in member/article_edit.php. Attackers can embed PHP code within a .jpg file and upload it via the templet parameter, then execute the malicious code to achieve remote code execution.
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<= 5.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if DedeCMS is installed and identify its versionLook for version information in the /data/admin/ver.txt file, or check the footer of the admin panel, or examine the /include/common.inc.php file for version constantsAffected if The installed version is Dedecms 5.6 or any version <= 5.6 (no specific version number visible indicates it may be an unpatched release)
-
Verify member/article_edit.php existsCheck if the file /member/article_edit.php is present in the web root directoryAffected if The file exists and is accessible without authentication restrictions
-
Check if member upload functionality is enabledLook for the $cfg_mb_upload and $cfg_mbtypes configuration values in /data/config.php or /include/common.inc.php, or attempt to access the member upload interface at /member/uploads.phpAffected if Member uploads are allowed ($cfg_mb_upload is not set to 'N' or disabled)
-
Inspect upload directory for PHP execution riskCheck the /uploads directory for any .htaccess files that disable PHP execution, or verify web server configuration allows PHP execution in upload directoriesAffected if PHP execution is allowed in the uploads directory (no restrictions in .htaccess or server config)
-
Review templet parameter handling in article_edit.phpExamine the /member/article_edit.php source code for how the 'templet' parameter is processed - look for lack of validation before file operationsAffected if The templet parameter accepts user input without proper sanitization and allows file writes to the uploads directory
A user is affected if they are running Dedecms version 5.6 or lower, the member/article_edit.php file exists, member uploads are enabled, and the templet parameter is not properly validated.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict and validate the templet parameter, implement strict file type validation for uploads, disable PHP execution in upload directories, and update to a patched version if available.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17727 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-17727 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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