dbcve.org
Shipping Multiple AddressesWordPress extension · Woocommerce

CVE-2023-51497

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-14
Fix available
A fix is available. Upgrade to 3.8.10 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Missing Authorization vulnerability in Woo WooCommerce Ship to Multiple Addresses.This issue affects WooCommerce Ship to Multiple Addresses: from n/a through 3.8.9.

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 confidence

Missing Authorization vulnerability in the WooCommerce Ship to Multiple Addresses plugin allows low-privileged users (such as customers or subscribers) to potentially access or modify shipping configurations and addresses belonging to other users or orders without proper capability checks. This is a classic IDOR (Insecure Direct Object Reference) or broken access control issue in the plugin's functionality.

MitigationUpdate the WooCommerce Ship to Multiple Addresses plugin to version 3.8.10 or later which contains the authorization fix. If immediate update is not possible, restrict user registration and monitor for suspicious access patterns to order shipments.

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
Affected:< 3.8.10

CVSS 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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the vulnerable plugin is installed
    Check your WordPress plugins directory or wp-admin plugins list for 'WooCommerce Ship to Multiple Addresses' or 'woocommerce-shipping-multiple-addresses'. In the filesystem, look under wp-content/plugins/ for a folder named similarly.
    Affected if The plugin folder exists in your WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the WooCommerce Ship to Multiple Addresses plugin. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file for a 'Version:' header or the readme.txt file.
    Affected if The version number is lower than 3.8.10 (e.g., 3.8.9, 3.8.8, etc.)
  3. Verify the plugin is active
    In WordPress admin, confirm the plugin status shows as 'Active' on the Plugins page.
    Affected if The plugin is currently active and running
  4. Confirm presence of low-privileged user accounts
    In WordPress admin, go to Users > All Users and review the roles assigned. Look for subscribers, customers, or other non-administrator roles that have access to the site.
    Affected if There are user accounts with roles other than Administrator (especially subscribers or customers) who can log in to the site
  5. Check for suspicious order shipping modifications
    Review WooCommerce order notes and the wc_order_stats table in the database for multiple different user_ids accessing or modifying shipping addresses on orders they do not own. Use query: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%_shipping%' and examine if multiple users modify the same order.
    Affected if Order shipping data shows modifications from user accounts that did not create the original order

Your environment is affected if the WooCommerce Ship to Multiple Addresses plugin is installed, active, and running version 3.8.9 or lower while having non-administrator user accounts on the site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.8.10 or later
Fixed in 3.8.10
Interim mitigation

Update the WooCommerce Ship to Multiple Addresses plugin to version 3.8.10 or later which contains the authorization fix. If immediate update is not possible, restrict user registration and monitor for suspicious access patterns to order shipments.

Recommended fix High confidence

3.8.10

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WooCommerce Ship to Multiple Addresses' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.8.10 or later
  5. 5. Verify the update completed successfully by checking the plugin version
  6. 6. Test the shipping functionality to ensure the plugin continues to work correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shipping Multiple Addresses Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51497 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51497 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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