dbcve.org
Product VendorsWordPress extension · Woocommerce

CVE-2023-51494

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 2.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Product Vendors.This issue affects WooCommerce Product Vendors: from n/a through 2.2.1.

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 WooCommerce Product Vendors plugin allows attackers to access functionality or data without proper authentication or authorization checks. The CVSS 9.8 score indicates this can likely be exploited by unauthenticated attackers to perform privileged actions.

MitigationUpdate WooCommerce Product Vendors to the latest patched version immediately to remediate this authorization bypass.

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
Product VendorsWordPress extension
Affected:< 2.2.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate WooCommerce Product Vendors plugin
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'WooCommerce Product Vendors' in the list of installed plugins.
    Affected if The plugin is installed and active on the WordPress site
  2. Find installed plugin version
    In the Plugins list, click on the plugin name to view details, or check the plugin header in the main plugin file (typically at wp-content/plugins/woocommerce-product-vendors/woocommerce-product-vendors.php) for the 'Version' comment.
    Affected if The displayed version number is lower than 2.2.2 (for example, 2.2.1, 2.2.0, 2.1.x, etc.)
  3. Verify the plugin is accessible to the web
    Confirm the plugin directory exists at wp-content/plugins/woocommerce-product-vendors/ and is not blocked via .htaccess or server configuration from external access.
    Affected if The plugin files are publicly accessible and the plugin is active

A site is affected if the WooCommerce Product Vendors plugin is installed and active with a version number lower than 2.2.2, as this version range contains the missing authorization vulnerability that can be exploited by unauthenticated attackers.

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 2.2.2 or later
Fixed in 2.2.2
Interim mitigation

Update WooCommerce Product Vendors to the latest patched version immediately to remediate this authorization bypass.

Recommended fix Moderate confidence

2.2.2

  1. 1. Backup your WordPress site database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the 'WooCommerce Product Vendors' plugin.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 2.2.2.
  5. 5. Alternatively, download version 2.2.2 from the WordPress plugin repository or your purchased source.
  6. 6. Deactivate and delete the current version, then upload and install version 2.2.2.
  7. 7. After upgrading, verify the plugin status shows version 2.2.2.
  8. 8. Test vendor functionality (product creation, order management, commission calculations) to confirm the upgrade did not break existing features.

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

Fix this in Product Vendors Scoped from the published advisory
  • Consultation3.0 h
  • Implementation1.0 h
  • Testing6.0 h
  • Review / QA4.0 h
14.0 hours of engineering $2,400
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,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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