CVE-2024-1849

WP Customer Reviews <= 3.7.0 - Authenticated (Contributor+) Malicious Redirect via HTTP-EQUIV Injection

2024-03-25 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 3.7.1
Affected Plugin
WP Customer Reviews
Affected Version
<= 3.7.0
CVSS
6.4Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2024-1849
View all WP Customer Reviews vulnerabilities

At a glance

CVE-2024-1849 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the WP Customer Reviews WordPress plugin, affecting versions <= 3.7.0. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.7.1; sites on affected versions should update now. Disclosed March 2024, reported by Dmitrii Ignatyev.

Vulnerability Overview

The WP Customer Reviews plugin for WordPress is vulnerable to malicious redirects in all versions up to, and including, 3.7.0. This is due to the plugin not properly validating the Business Name field. This makes it possible for authenticated attackers, with contributor-level access and above, to inject malicious redirects.

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

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

Reaching this weakness in WP Customer Reviews <= 3.7.0 takes an account at Contributor level or above. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For WP Customer Reviews the fix is 3.7.1: builds <= 3.7.0 are affected, anything from 3.7.1 onward is not.

Remediation

Update to version 3.7.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Customer Reviews 3.7.1 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