CVE-2025-12130 MEDIUM

CVE-2025-12130: WC Vendors – WooCommerce Multivendor, WooCommerce Marketplace, Product Vendors <= 2.6.4 - Cross-Site Request Forgery to Vendor Product Deletion

Vendor Wcvendors
Product WC Vendors – WooCommerce Multivendor, WooCommerce Marketplace, Product Vendors
Weakness CWE-352 · CSRF
Published December 5, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

The WC Vendors – WooCommerce Multivendor, WooCommerce Marketplace, Product Vendors plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.6.4. This is due to missing or incorrect nonce validation on the /vendor_dashboard/product/delete/ endpoint. This makes it possible for unauthenticated attackers to delete vendor products via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

WC Vendors contains a cross-site request forgery (CSRF) vulnerability affecting versions up to 2.6.4. An attacker can craft a malicious link or page that, when visited by a logged-in site administrator or vendor, performs unwanted actions on their behalf. The vulnerability requires user interaction and does not expose sensitive data, but can modify site content or settings.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions (like changing settings or creating listings) on behalf of a logged-in vendor or admin.

Potential impact on your site

04Site Impact

Vendors or admins could unknowingly authorize changes to marketplace settings, listings, or account details.

Conditions required to exploit

05Prerequisites

Victim must be logged in and click a malicious link or visit an attacker-controlled page.

Key dates

06Disclosure timeline

December 5, 2025 CVE published
April 8, 2026 Record updated