dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-1311

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 Multivendor Marketplace – REST API plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter in the update_delivery_status() function in all versions up to, and including, 1.6.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Multivendor Marketplace REST API plugin has a SQL injection vulnerability in the update_delivery_status() function. The 'id' parameter is not properly escaped and the SQL query lacks prepared statements, allowing authenticated attackers with Subscriber-level access to inject malicious SQL queries and extract sensitive data from the database.

MitigationUpdate the plugin to version 1.6.3 or later which contains the fix. Until patched, consider restricting subscriber-level API access and monitor logs for suspicious SQL patterns.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'WooCommerce Multivendor Marketplace' (or 'WooCommerce Marketplace' plugin), and note the installed version number.
    Affected if The installed version is below 1.6.3 (e.g., 1.6.2, 1.6.1, 1.5.x, etc.)
  2. Verify REST API is accessible
    Make a GET request to the site's REST API endpoint (usually /wp-json/ or /wp-json/wc/v3/) and confirm the API responds without being blocked by firewall or authentication rules.
    Affected if The REST API endpoint is publicly accessible or accessible to authenticated users with Subscriber role
  3. Check for Subscriber-level user accounts
    In WordPress admin > Users, review the list of users and identify any accounts assigned the 'Subscriber' role.
    Affected if At least one user account with Subscriber role exists in the system
  4. Identify vulnerable endpoint exposure
    Test access to the update_delivery_status endpoint by examining plugin REST API routes (often at /wp-json/wvm/v1/delivery/status or similar path under the vendor marketplace namespace).
    Affected if The plugin's delivery status update endpoint is accessible to authenticated requests
  5. Review API access controls
    Check WordPress REST API settings via plugin configurations or site settings to confirm whether subscriber-role users can make POST/PUT requests to the vendor marketplace API endpoints.
    Affected if Subscriber-level users are permitted to make API calls to vendor marketplace endpoints

You are affected if the WooCommerce Multivendor Marketplace plugin is installed with a version lower than 1.6.3 AND your REST API is accessible to users with Subscriber role.

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 plugin to version 1.6.3 or later which contains the fix. Until patched, consider restricting subscriber-level API access and monitor logs for suspicious SQL patterns.

Recommended fix High confidence

Latest version after 1.6.2 (e.g., 1.6.3 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WooCommerce Multivendor Marketplace – REST API' plugin
  4. 4. Check the current version number to confirm it is 1.6.2 or below
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the latest version from wordpress.org and upload it manually via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the new version number in the Plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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