CVE-2019-6289
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 · unediteduploads/include/dialog/select_soft.php in DedeCMS V57_UTF8_SP2 allows remote attackers to execute arbitrary PHP code by uploading with a safe file extension and then renaming with a mixed-case variation of the .php extension, as demonstrated by the 1.pHP filename.
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 V57_UTF8_SP2 has a file upload vulnerability in uploads/include/dialog/select_soft.php. The application validates file extensions but does so in a case-sensitive manner, allowing attackers to bypass the filter by using mixed-case extensions like .pHP instead of .php. After uploading with a safe extension, renaming the file with a mixed-case PHP extension enables arbitrary PHP 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.7CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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.
-
Identify DedeCMS installationLook for DedeCMS directories and files in the web root, typically in /uploads/, /include/, or /dede/ folders. Check for characteristic DedeCMS files like index.php with DedeCMS content or the /uploads/include/dialog/ directory structure.Affected if DedeCMS is present in the web environment and the version matches 5.7 (or is unknown/unversioned but appears to be DedeCMS)
-
Determine DedeCMS versionCheck for version file or header in common locations such as /data/admin/ver.txt, or view page source of any DedeCMS admin page for version comments. Also check the filename in the CVE: V57_UTF8_SP2 indicates version 5.7.Affected if The installed version is DedeCMS 5.7 (or cannot be determined but is DedeCMS)
-
Locate vulnerable file select_soft.phpCheck if the file uploads/include/dialog/select_soft.php exists in the web directory. This is the specific file containing the vulnerability.Affected if The file select_soft.php exists in the expected path within the DedeCMS installation
-
Verify file upload functionality is enabledCheck if the DedeCMS upload module is active by attempting to access the file upload dialog through the admin panel, or inspect /data/config.php for upload-related settings.Affected if File upload functionality is enabled and accessible (particularly in the soft upload dialog in admin area)
-
Check web server PHP execution in upload directoriesInspect web server configuration (Apache .htaccess, Nginx config) for the upload directories (/uploads/) to see if PHP execution is explicitly disabled.Affected if PHP execution is NOT explicitly disabled in upload directories (meaning the uploaded file could be executed if renamed to .php)
A user is affected if DedeCMS version 5.7 is installed, the vulnerable select_soft.php file exists, file uploads are enabled, and PHP execution is allowed in upload directories.
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 dataImplement case-insensitive extension validation for all uploaded files and rename uploaded files to remove potentially dangerous extensions. Additionally, configure the web server to disable PHP execution in upload directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6289 — 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-2019-6289 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