dbcve.org
Shipping Multiple AddressesWordPress extension · Woocommerce

CVE-2023-32799

MEDIUM · 6.5 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to after 3.8.3 or later.
See remediation →
71/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
Authorization Bypass Through User-Controlled Key vulnerability in WooCommerce Shipping Multiple Addresses.This issue affects Shipping Multiple Addresses: from n/a through 3.8.3.

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

This is an authorization bypass vulnerability where the WooCommerce Shipping Multiple Addresses plugin (versions through 3.8.3) uses user-controlled keys to determine access to shipping functionality without proper authorization validation. An authenticated attacker could potentially access or modify shipping addresses or delivery configurations they shouldn't have permission to access.

MitigationUpdate the WooCommerce Shipping Multiple Addresses plugin to the latest version once available, and ensure all requests involving user-controlled keys include server-side authorization validation to confirm the current user has permission for the requested resource.

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.3

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Verify the plugin version
    Access your WordPress admin dashboard, go to Plugins > Installed Plugins, locate 'WooCommerce Shipping Multiple Addresses', and check the version number displayed. Alternatively, inspect the plugin's main PHP file header for the Version field.
    Affected if The installed version is 3.8.3 or lower.
  2. Confirm the plugin is active
    In the WordPress admin under Plugins > Installed Plugins, verify that 'WooCommerce Shipping Multiple Addresses' shows as 'Active' rather than 'Inactive'.
    Affected if The plugin is active and the version is 3.8.3 or lower.
  3. Check for user-controlled key handling in shipping requests
    Review server-side logs or HTTP request patterns for the plugin's shipping address endpoints. Look for requests that include a user-controlled parameter (such as an address ID, key, or token) that could be manipulated to access other users' shipping data.
    Affected if The plugin processes requests where shipping address identifiers are derived directly from user input without server-side authorization verification.
  4. Inspect the plugin's authorization logic
    Examine the plugin's PHP code, specifically functions handling shipping address retrieval, modification, or delivery configuration. Look for code that uses user-supplied values to determine which shipping data to load without validating the current user's ownership of that resource.
    Affected if The code uses user-controlled keys to determine access to shipping functionality without calling current_user_can() or equivalent WordPress authorization checks.

You are affected if the WooCommerce Shipping Multiple Addresses plugin is active at version 3.8.3 or lower and the plugin processes shipping-related requests using user-supplied identifiers without verifying user ownership.

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.

From vendor data
Upgrade available Upgrade to a release after 3.8.3
Interim mitigation

Update the WooCommerce Shipping Multiple Addresses plugin to the latest version once available, and ensure all requests involving user-controlled keys include server-side authorization validation to confirm the current user has permission for the requested resource.

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-32799 — 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-32799 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