Shipping Multiple AddressesWordPress extension · Woocommerce
CVE-2023-37873
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in WooCommerce Shipping Multiple Addresses plugin <= 3.8.5 versions.
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 confidenceAn unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the WooCommerce Shipping Multiple Addresses plugin for WordPress, affecting versions 3.8.5 and below. The vulnerability allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in the application's response.
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
Shipping Multiple AddressesWordPress extension
<= 3.8.5CVSS 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.1/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.
-
Verify the plugin is installedCheck your WordPress plugins directory or the installed plugins list in the WordPress admin panel under Plugins > Installed Plugins. Look for 'WooCommerce Shipping Multiple Addresses' in the list.Affected if The plugin is present in the WordPress installation regardless of activation status.
-
Check the installed versionIn the WordPress admin, go to Plugins > Installed Plugins and find the WooCommerce Shipping Multiple Addresses plugin. The version number is displayed below the plugin name. Alternatively, check the main plugin file (e.g., woocommerce-shipping-multiple-addresses.php) and look for the Version header comment.Affected if The installed version is 3.8.5 or lower.
-
Confirm the plugin is activeIn WordPress admin, verify the WooCommerce Shipping Multiple Addresses plugin shows as 'Active' under the plugin status column.Affected if The plugin is active and accessible on the frontend.
-
Check if the vulnerable functionality is exposedIdentify pages or endpoints where the plugin's shipping multiple addresses functionality is accessible to unauthenticated users. Look for pages that handle shipping address input that may reflect user-supplied data back in the response.Affected if The plugin's address input forms are accessible to unauthenticated users without additional access controls.
You are affected if the WooCommerce Shipping Multiple Addresses plugin is installed with version 3.8.5 or lower and the shipping address functionality is accessible to visitors or unauthenticated users.
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 the WooCommerce Shipping Multiple Addresses plugin to a version newer than 3.8.5. If no patched version is available, apply output encoding/sanitization to all user-supplied input in the affected code paths.
Fix this in Shipping Multiple Addresses
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37873 — 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-2023-37873 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