dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49263

HIGH · 7.6 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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 WCVendors WC Vendors Marketplace wc-vendors allows Blind SQL Injection.This issue affects WC Vendors Marketplace: from n/a through <= 2.5.6.

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

Blind SQL Injection vulnerability in WC Vendors Marketplace plugin (wc-vendors) up to version 2.5.6 allows unauthenticated attackers to inject malicious SQL queries via unsanitized input parameters. The 'blind' classification means attackers infer database information through response differences or time-based observations rather than seeing direct output.

MitigationUpgrade WC Vendors Marketplace to the latest version immediately. If no patched version is available, disable the plugin until a fix is released, or implement input validation and convert vulnerable database queries to parameterized prepared statements.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L

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. Confirm WC Vendors plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'WC Vendors Marketplace' or 'WC Vendors' in the list. Alternatively, check the file system for /wp-content/plugins/wc-vendors/ directory.
    Affected if The plugin directory /wp-content/plugins/wc-vendors/ exists or the plugin appears in the WordPress plugins list
  2. Identify the installed version number
    In WordPress admin, find the plugin in the Installed Plugins list and note the version number displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/wc-vendors/wc-vendors.php for the 'Version' field.
    Affected if The version number is 2.5.6 or lower, or if no version is displayed and the plugin appears to be an older installation
  3. Verify the plugin is active and accessible
    In WordPress admin, confirm the plugin status shows 'Active'. Since this is an unauthenticated vulnerability, check that the WordPress site is publicly accessible and the plugin handles front-end vendor functionality.
    Affected if The plugin is active and the site is publicly accessible, meaning the vulnerable endpoints can be reached without authentication
  4. Check for exposure of vendor-related endpoints
    Common entry points for this vulnerability would be vendor submission or registration forms. Inspect the site for URLs containing /vendor/, /pv_vendor/, or check the WC Vendors settings at WooCommerce > WC Vendors > Settings.
    Affected if Vendor functionality endpoints are accessible on the front end, which would allow the unsanitized SQL injection parameters to be submitted

If WC Vendors Marketplace plugin version 2.5.6 or lower is installed and active with vendor endpoints accessible, the environment is vulnerable to unauthenticated blind SQL injection.

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

Upgrade WC Vendors Marketplace to the latest version immediately. If no patched version is available, disable the plugin until a fix is released, or implement input validation and convert vulnerable database queries to parameterized prepared statements.

Recommended fix Moderate confidence

Version 2.5.7 or latest release

  1. Create a full backup of your WordPress site before making any changes
  2. Update WC Vendors Marketplace plugin to the latest available version (version 2.5.7 or later) via WordPress admin dashboard under Plugins > All Plugins, or via wp-cli: wp plugin update wc-vendors
  3. Verify the update was successfully applied by checking the plugin version in Plugins > Installed Plugins
  4. Clear any caching mechanisms if your site uses caching (site cache, server-side cache, CDN cache)
  5. Test critical vendor functionalities on your site to ensure the update did not break existing features

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

Have this fixed 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 help mitigating

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-2025-49263 — 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-49263 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