CVE-2025-1311 MEDIUM

CVE-2025-1311: WooCommerce Multivendor Marketplace – REST API <= 1.6.2 - Authenticated (Subscriber+) SQL Injection

Vendor Wclovers
Product WCFM – Multivendor Marketplace REST API for WooCommerce
Weakness CWE-89 · SQLi
Published March 22, 2025
Last update April 8, 2026

CVSS base score

6.5/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity None

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

WCFM Multivendor Marketplace REST API for WooCommerce versions 1.6.2 and earlier contain a SQL injection vulnerability in the REST API. An authenticated attacker with low privileges can craft malicious API requests to read sensitive data from the database, including user information and other confidential records. The vulnerability requires valid user credentials but no additional user interaction.

What an attacker can do

03Attacker Capabilities

Read sensitive data from the site's database, including user records and other confidential information.

Potential impact on your site

04Site Impact

User data and other sensitive database records may be exposed to authenticated attackers with basic account access.

Conditions required to exploit

05Prerequisites

Attacker must have a valid user account with low-level privileges on the site.

Key dates

06Disclosure timeline

March 22, 2025 CVE published
April 8, 2026 Record updated