CVE-2017-11675
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 · uneditedThe traverseStrictSanitize function in admin_dir/includes/classes/AdminRequestSanitizer.php in ZenCart 1.5.5e mishandles key strings, which allows remote authenticated users to execute arbitrary PHP code by placing that code into an invalid array index of the admin_name array parameter to admin_dir/login.php, if there is an export of an error-log entry for that invalid array index.
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 confidenceZenCart 1.5.5e contains a code injection vulnerability in the traverseStrictSanitize function within AdminRequestSanitizer.php. The function fails to properly sanitize invalid array indices in the admin_name parameter, allowing authenticated admin users to inject arbitrary PHP code that gets executed when error logs containing those indices are exported.
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= 1.5.5eCVSS 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.
-
Verify ZenCart installation versionLocate the version file in your ZenCart installation (typically includes a version.php or includes/application_top.php with version constants) and check if the version is 1.5.5eAffected if The installed version is exactly 1.5.5e (this is the only version listed as affected)
-
Confirm AdminRequestSanitizer.php existsLocate the file AdminRequestSanitizer.php within the ZenCart admin directory structure (typically in includes/classes/)Affected if The file exists in the expected location, indicating the vulnerable component is present
-
Check for the traverseStrictSanitize functionOpen AdminRequestSanitizer.php and search for the function named traverseStrictSanitizeAffected if The function exists in the code, confirming the vulnerable function is present
-
Verify admin authentication is possibleDetermine if the system allows admin user authentication. Check if admin accounts exist and login functionality is operationalAffected if An authenticated admin user can access the system, which is required to exploit this vulnerability
-
Confirm error logging export feature is accessibleLocate and inspect the error logging or log export functionality within the admin panel that handles the error logs containing array indicesAffected if Error log export functionality is enabled and accessible to authenticated admins, which is required to trigger the injected code execution
You are affected if you are running ZenCart version 1.5.5e, the AdminRequestSanitizer.php with the traverseStrictSanitize function is present, and authenticated admin access exists with enabled error log export functionality.
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 dataUpdate to a patched version of ZenCart that properly validates array indices in the AdminRequestSanitizer class and ensures error logging does not execute injected code from invalid array keys. Consider disabling or hardening the error-log export functionality until patched.
- Consultation3.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11675 — 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-11675 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