CVE-2018-9175
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 5.7 allows remote attackers to execute arbitrary PHP code via the egroup parameter to uploads/dede/stepselect_main.php because code within the database is accessible to uploads/dede/sys_cache_up.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 5.7 contains a critical code execution vulnerability where the egroup parameter in uploads/dede/stepselect_main.php allows attackers to inject and execute arbitrary PHP code. The sys_cache_up.php file improperly handles code stored in the database, enabling remote code execution without proper authentication or input sanitization.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 versionCheck the version.php file in the DedeCMS root directory, typically found at /include/version.php or /data/admin/ver.txt. Alternatively, look for version information in the admin login page footer or /data/config.php.Affected if The installed version is DedeCMS 5.7 exactly.
-
Verify vulnerable file existenceCheck if the file uploads/dede/stepselect_main.php exists in the web root. Also verify that /include/sys_cache_up.php exists.Affected if Both stepselect_main.php and sys_cache_up.php files are present in the expected locations.
-
Check /dede/ admin directory accessAttempt to access the /dede/ directory via HTTP from an unauthenticated browser or curl command. Check if web server returns a response rather than a 403/401 redirect to login.Affected if The /dede/ admin directory is accessible without authentication or allows unauthenticated parameter injection.
-
Verify PHP execution in uploads directoryInspect web server configuration (Apache .htaccess, Nginx config, or IIS URL Rewrite rules) to determine if PHP execution is permitted in the /uploads/ directory.Affected if PHP execution is allowed in the uploads/ directory, enabling arbitrary code injection to execute.
A system is affected if it runs DedeCMS version 5.7, has the vulnerable PHP files present, and allows unauthenticated access to the /dede/ directory with PHP execution enabled in uploads.
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 dataApply available vendor patches immediately; if no patch exists, disable PHP execution in upload directories and restrict network access to the /dede/ admin area using web server filters or firewall rules.
- Consultation2.0 h
- Implementation6.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 $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-9175 — 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-2018-9175 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