CVE-2023-36514
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 · uneditedCross-Site Request Forgery (CSRF) 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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in WooCommerce Shipping Multiple Addresses plugin versions 3.8.5 and below allows remote attackers to trick authenticated users into executing unintended shipping-related actions through maliciously crafted requests.
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<= 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify if the plugin is installedCheck your WordPress site's wp-content/plugins/ directory for a folder named 'woocommerce-shipping-multiple-addresses' or 'woocommerce-multi-address-shipping'. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to look for 'WooCommerce Shipping Multiple Addresses' in the list.Affected if The plugin folder or entry is found in the installed plugins directory
-
Check the installed plugin versionIn 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, open the main plugin file (usually named main.php or woocommerce-shipping-multiple-addresses.php) in the plugin folder and look for the Version header in the plugin comments.Affected if The version displayed is 3.8.5 or any version lower than 3.8.5
-
Confirm the plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that the WooCommerce Shipping Multiple Addresses plugin shows as 'Active' (the plugin toggle is in the enabled position).Affected if The plugin is active and running on the site
-
Verify the CSRF vulnerability appliesSince this is a CSRF flaw, it requires an authenticated user session to be exploited. Check if users with access to the shipping multiple addresses functionality (such as customers placing orders or admins managing shipments) exist and could be targeted. This check is informational about exposure scope.Affected if Authenticated users with shipping capabilities access the site and the plugin is active
Your site is affected if the WooCommerce Shipping Multiple Addresses plugin is installed, active, and running version 3.8.5 or lower.
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, or apply vendor-supplied patch if available; alternatively disable the plugin until a fix is released.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36514 — 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-36514 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