dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-4335

HIGH · 8.8 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The Woocommerce Multiple Addresses plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.0.7.1. This is due to insufficient restrictions on user meta that can be updated through the save_multiple_shipping_addresses() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges to that of an administrator.

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 confidence

The WooCommerce Multiple Addresses plugin for WordPress contains a privilege escalation vulnerability in the save_multiple_shipping_addresses() function. Authenticated users with Subscriber-level access can manipulate user meta data through this function to elevate their privileges to administrator level due to missing capability checks and improper authorization on user meta updates.

MitigationUpdate the WooCommerce Multiple Addresses plugin to version 1.0.8 or later, which contains proper authorization checks. Until then, restrict subscriber-level account creation and monitor for suspicious privilege changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

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

  1. Verify WooCommerce Multiple Addresses plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WooCommerce Multiple Addresses' or check the plugin files in wp-content/plugins/woocommerce-multiple-addresses/
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    Look at the plugin version number in the plugin header (usually in the main PHP file or readme.txt), or view it in the WordPress plugin admin page
    Affected if Version is lower than 1.0.8 or the version cannot be determined (unknown if patch was applied)
  3. Verify user role configuration allows Subscriber-level access
    In WordPress admin, go to Users > Roles and check if Subscriber role exists and has not been removed; also check if any custom roles permit front-end access to the plugin's address saving functionality
    Affected if Subscriber role or equivalent low-privilege role exists and can access the site front-end where the plugin exposes address forms
  4. Inspect for unauthorized Administrator accounts
    In WordPress admin, go to Users > All Users and review the list of Administrator accounts; check user metadata (via database query: SELECT * FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%administrator%') for unexpected admin accounts created around the time the plugin was active
    Affected if There are Administrator accounts you did not create, or accounts with modified capabilities that coincide with the plugin's activation period

You are affected if the WooCommerce Multiple Addresses plugin is installed with a version prior to 1.0.8 and low-privilege users (Subscriber level or below) can access the site front-end where address forms are rendered.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WooCommerce Multiple Addresses plugin to version 1.0.8 or later, which contains proper authorization checks. Until then, restrict subscriber-level account creation and monitor for suspicious privilege changes.

Recommended fix High confidence

Version 1.0.8 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Woocommerce Multiple Addresses' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4335 — 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-2025-4335 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