WooCommerce Reviews Plugin with Multi-criteria Rating by ReviewX < 1.2.9 - Cross-Site Request Forgery

2021-06-30 00:00
WPScanTeam

Strategic Overview

Status
Patched in 1.2.9
Affected Version
< 1.2.9
CVSS
8.3High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all ReviewX – Multi-Criteria Reviews for WooCommerce with Google Reviews & Schema vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the ReviewX WordPress plugin, affecting versions < 1.2.9. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.9; sites on affected versions should update now. Disclosed June 2021, reported by WPScanTeam.

Vulnerability Overview

The WooCommerce Reviews Plugin with Multi-criteria Rating by ReviewX plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions before 1.2.9. This is due to missing nonce validation in the ~/app/Controllers/Storefront/ReviewxPublic.php file. This makes it possible for unauthenticated attackers to perform unauthorized AJAX actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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, and no interaction from a victim user.

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

Reaching this weakness in ReviewX < 1.2.9 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 ReviewX the fix is 1.2.9: builds < 1.2.9 are affected, anything from 1.2.9 onward is not.

Remediation

Update to version 1.2.9, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to ReviewX: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ReviewX 1.2.9 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