CVE-2024-25929

Product Catalog Enquiry for WooCommerce by MultiVendorX <= 5.0.5 - Cross-Site Request Forgery via REST API

2024-02-20 00:00
Abdi Pranata

Strategic Overview

Status
Patched in 5.0.6
Affected Version
<= 5.0.5
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-25929
View all CatalogX – Catalog Mode, Enquiry & Quotes for WooCommerce vulnerabilities

At a glance

CVE-2024-25929 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the CatalogX WordPress plugin, affecting versions <= 5.0.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.0.6; sites on affected versions should update now. Disclosed February 2024, reported by Abdi Pranata.

Vulnerability Overview

The Product Catalog Enquiry for WooCommerce by MultiVendorX plugin for WordPress is vulnerable to cross-site request forgery due to an improper capability check on the 'catalog_permission' function in versions up to, and including, 5.0.5. While the REST endpoints are only initialized for administrator users, the fact that the 'catalog_permission' returns true means that the REST route is treated as unauthenticated and thus does not require a REST nonce. This makes it possible for unauthenticated attackers to save enquiries.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

CatalogX <= 5.0.5 carries this weakness at catalog_permission, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For CatalogX the fix is 5.0.6: builds <= 5.0.5 are affected, anything from 5.0.6 onward is not.

Remediation

Update to version 5.0.6, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to CatalogX: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CatalogX 5.0.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C