dbcve.org
Product VendorsWordPress extension · Woo

CVE-2023-52186

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 2.2.3 or later.
See remediation →
62/100
Remediation priority · Elevated
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.2.

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 unauthenticated or unauthorized users to access certain vendor-related functionality due to missing capability checks or authentication verification on sensitive endpoints.

MitigationImplement proper authorization checks including capability verification and nonce validation on all vendor-related functions and admin actions to ensure only authenticated users with appropriate permissions can access sensitive operations.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Check installed plugin version
    Navigate to WordPress Admin > Plugins and locate 'WooCommerce Product Vendors' (or 'Woo Product Vendors'), or inspect the plugin's main PHP file header for the 'Version' field. Compare the version number against the affected range: versions prior to 2.2.3 are vulnerable.
    Affected if Installed version is less than 2.2.3
  2. Identify if vendor functionality is active
    Check the WordPress site for active vendor-related features: look for vendor registration pages, vendor dashboard endpoints, or any custom post types/taxonomies related to vendors that may have been created.
    Affected if Vendor functionality or vendor user roles are enabled on the site
  3. Verify endpoint accessibility
    Test access to any vendor-related admin actions or public-facing vendor functions by submitting requests without authentication or with a low-privilege user account to see if sensitive operations execute.
    Affected if Requests to vendor functions complete without requiring proper capability verification or authentication

The environment is affected if the Woo Product Vendors plugin version is below 2.2.3 and vendor functionality is active, allowing unauthenticated or unauthorized access to sensitive vendor operations.

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.3 or later
Fixed in 2.2.3
Interim mitigation

Implement proper authorization checks including capability verification and nonce validation on all vendor-related functions and admin actions to ensure only authenticated users with appropriate permissions can access sensitive operations.

Recommended fix High confidence

WooCommerce Product Vendors 2.2.3

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate WooCommerce Product Vendors in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install version 2.2.3 or later.
  5. 5. Alternatively, upload the version 2.2.3 plugin files manually via FTP or the WordPress plugin uploader if automatic updates are not working.
  6. 6. After updating, clear any caching mechanisms and verify the plugin is running version 2.2.3 or newer.
  7. 7. Test that vendor functionality works correctly, particularly any areas where authorization checks were previously missing.

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

Fix this in Product Vendors Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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