CVE-2018-16320
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 · uneditedidreamsoft iCMS 7.0.11 allows admincp.php?app=config Directory Traversal, resulting in execution of arbitrary PHP code from a ZIP file.
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 · moderate confidenceidreamsoft iCMS 7.0.11 contains a directory traversal vulnerability in admincp.php?app=config that allows authenticated administrators to traverse filesystem directories and write/extract arbitrary files, including PHP code from ZIP archives, leading to 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= 7.0.11CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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.
-
Confirm iCMS version installedLocate and read the version file or header in the iCMS installation directory. Common paths include a version.php, about.php, or check the footer/meta of admin pages. Compare the version number to 7.0.11.Affected if The installed version is exactly 7.0.11
-
Verify admincp.php existsCheck for the presence of admincp.php in the web root or admin directory of the iCMS installation.Affected if admincp.php exists and is accessible via the web server
-
Confirm app=config parameter handling existsInspect the source code of admincp.php to verify it processes an 'app' parameter and specifically contains logic for 'config' application handling.Affected if The code contains an app parameter handler that routes to config functionality
-
Check for ZIP extraction functionalityExamine the config handling code for functions that process file uploads, ZIP archives, or file extraction operations that accept user-controlled paths.Affected if The code contains ZIP extraction or file write operations that use path parameters controllable by the user
-
Verify administrator authentication is requiredReview the access control logic in admincp.php to confirm that administrator authentication is enforced before allowing the vulnerable file operation.Affected if The vulnerable endpoint requires only authenticated administrator access (not publicly exposed)
Your environment is affected if you are running iCMS version 7.0.11 with admincp.php accessible to authenticated administrators and the config app contains the vulnerable ZIP extraction/file write logic.
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 strict input validation on file path parameters to prevent directory traversal sequences (..). Additionally, validate and sanitize ZIP extraction paths to ensure extracted files remain within intended directories. Consider restricting admin access and applying principle of least privilege.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16320 — 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-16320 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