Woocommerce Pdf Invoices\& Packing SlipsWordPress extension · Wpovernight
CVE-2017-18506
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 woocommerce-pdf-invoices-packing-slips plugin before 2.0.13 for WordPress has XSS via the tab or section variable on settings screens.
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 woocommerce-pdf-invoices-packing-slips plugin before version 2.0.13 contains a stored cross-site scripting (XSS) vulnerability in the settings screens. The tab or section parameter on the settings pages is not properly sanitized, allowing attackers to inject malicious JavaScript that executes when administrators access those settings pages.
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
Woocommerce Pdf Invoices\& Packing SlipsWordPress extension
< 2.0.13CVSS 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 the installed version of the woocommerce-pdf-invoices-packing-slips pluginNavigate to WordPress admin > Plugins > Installed Plugins, locate 'WooCommerce PDF Invoices & Packing Slips' by WPOvernight, and note the version number displayedAffected if The version listed is below 2.0.13 (for example, 2.0.12, 2.0.10, 1.x.x, etc.)
-
Confirm the plugin is activeIn the same plugins list, verify that the plugin shows as 'Active' under the status columnAffected if The plugin is active and the version is below 2.0.13
-
Verify access to plugin settings is possibleNavigate to WooCommerce > PDF Invoices (or the plugin settings menu item) to confirm the settings pages are accessible in the current installationAffected if Settings pages are accessible and the plugin version is below 2.0.13
You are affected if the woocommerce-pdf-invoices-packing-slips plugin is active and the installed version is below 2.0.13, as the stored XSS vulnerability exists in the unsanitized tab/section parameters on the plugin settings screens.
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 data2.0.13
Update the woocommerce-pdf-invoices-packing-slips plugin to version 2.0.13 or later to remediate the XSS vulnerability. As this is a stored XSS with medium CVSS score, prioritize the update given the attack vector is through authenticated admin access to settings.
Fix this in Woocommerce Pdf Invoices\& Packing Slips
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18506 — 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-18506 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