EshopWordPress extension · Eshop Project
CVE-2015-3421
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 eshop_checkout function in checkout.php in the Wordpress Eshop plugin 6.3.11 and earlier does not validate variables in the "eshopcart" HTTP cookie, which allows remote attackers to perform cross-site scripting (XSS) attacks, or a path disclosure attack via crafted variables named after target PHP variables.
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 confidenceThe WordPress Eshop plugin versions 6.3.11 and earlier contain an XSS vulnerability in the eshop_checkout function within checkout.php. The function fails to validate or sanitize variables stored in the eshopcart HTTP cookie before using them in the page output, allowing attackers to inject malicious scripts. Additionally, the lack of validation on cookie parameter names enables path disclosure attacks by exposing server file paths through crafted variable names.
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
EshopWordPress extension
<= 6.3.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Eshop plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > Eshop and locate the version number in the plugin header, or inspect the main plugin file (e.g., wp-content/plugins/eshop/eshop.php) for the 'Version:' field in the plugin header commentAffected if The displayed version is 6.3.11 or lower
-
Locate the vulnerable checkout.php fileCheck if wp-content/plugins/eshop/checkout.php exists on the serverAffected if The file exists in the plugin directory
-
Verify the eshop_checkout function handles the eshopcart cookieOpen checkout.php and search for the eshop_checkout function definition, then locate where it processes the eshopcart cookie (look for $_COOKIE['eshopcart'] or similar) and outputs it without sanitizationAffected if The function reads from eshopcart cookie and outputs it directly to the page without htmlspecialchars or similar sanitization
-
Check cookie parameter validationIn checkout.php, examine how the eshop_checkout function handles cookie variable names - look for any code that processes cookie keys as variable names (e.g., using extract() on cookie data or directly accessing $_COOKIE['eshopcart'] array keys in output)Affected if Cookie parameter names are used directly in output or in variable creation without validation
The environment is affected if the Eshop plugin version is 6.3.11 or earlier AND the checkout.php file exists with the vulnerable eshop_checkout function that outputs eshopcart cookie data without sanitization.
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 dataUpgrade the Eshop plugin to a version newer than 6.3.11, or implement proper input validation and output encoding on the eshopcart cookie parameters in the eshop_checkout function to prevent XSS and path disclosure.
Fix this in Eshop
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3421 — 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-2015-3421 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