dbcve.org
Product VendorsWordPress extension · Woo

CVE-2023-33331

HIGH · 7.2 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to 2.1.77 or later.
See remediation →
78/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WooCommerce Product Vendors allows SQL Injection.This issue affects Product Vendors: from n/a through 2.1.76.

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

SQL injection vulnerability in WooCommerce Product Vendors plugin allows attackers to inject malicious SQL commands through unsanitized input parameters, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate WooCommerce Product Vendors to the latest patched version beyond 2.1.76, or apply vendor-supplied security patch that implements proper input sanitization and parameterized queries.

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

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

CVSS:3.1/AV:N/AC:L/PR:H/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 the WooCommerce Product Vendors plugin installation
    Check your WordPress wp-content/plugins/ directory for a folder named 'woocommerce-product-vendors' or similar vendor-related plugin folder. Alternatively, list installed plugins via WP-CLI command: wp plugin list --status=active --format=csv | grep -i vendor
    Affected if The plugin folder or active plugin listing is not found, meaning the plugin is not installed and you are not affected.
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically the primary .php file in the plugin folder) and locate the 'Version:' field in the plugin header comment at the top. Alternatively, check the plugin's readme.txt file in the plugin folder for the version number.
    Affected if No version information is found in the plugin files.
  3. Compare the version against the affected range
    Compare the identified version number to the affected range: versions prior to 2.1.77 are vulnerable. For example, if your version shows 2.1.76, 2.1.70, or any version below 2.1.77, it falls within the affected range.
    Affected if The installed version is a three-part number where the first part is less than 2, or equals 2 and the second part is less than 1, or equals 2.1 and the third part is less than 77. Any version below 2.1.77 is affected.
  4. Verify the plugin is active
    If the plugin is installed but disabled, the SQL injection vulnerability is not exploitable in your environment. Check via WordPress admin Plugins page or WP-CLI: wp plugin status woocommerce-product-vendors
    Affected if The plugin is installed AND active. Only active plugins with versions below 2.1.77 are exploitable.

Your environment is affected only if WooCommerce Product Vendors plugin is installed, is currently active, and the version number is below 2.1.77.

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.1.77 or later
Fixed in 2.1.77
Interim mitigation

Update WooCommerce Product Vendors to the latest patched version beyond 2.1.76, or apply vendor-supplied security patch that implements proper input sanitization and parameterized queries.

Recommended fix High confidence

2.1.77

  1. Create a complete backup of the WordPress site and database before making any changes
  2. Log in to the WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate the 'WooCommerce Product Vendors' plugin
  5. Check the current version to confirm it is below 2.1.77
  6. Click 'Update Now' to install version 2.1.77 or later
  7. After updating, verify the new version number in the plugins list
  8. Test critical vendor-related functionality (product management, commission calculations, vendor dashboards) to confirm the update 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
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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