Plugin for Google Reviews <= 2.2.2 - Cross-Site Request Forgery

2022-11-16 00:00
Anonymous

Strategic Overview

Status
Patched in 2.2.3
Affected Plugin
Rich Showcase for Google Reviews
Affected Version
<= 2.2.2
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Rich Showcase for Google Reviews vulnerabilities

At a glance

This record tracks a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Rich Showcase for Google Reviews WordPress plugin, affecting versions <= 2.2.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.2.3; sites on affected versions should update now. Disclosed November 2022.

Vulnerability Overview

The Plugin for Google Reviews for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.2.2. This is due to missing or incorrect nonce validation on the save function. This makes it possible for unauthenticated attackers to create widgets, via forged request granted they can trick a site user 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in Rich Showcase for Google Reviews <= 2.2.2 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 Rich Showcase for Google Reviews the fix is 2.2.3: builds <= 2.2.2 are affected, anything from 2.2.3 onward is not.

Remediation

Update to version 2.2.3, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/e5ca3c84-9d3d-4bbe-90f7-44c9d77a6690

Related records

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