CVE-2022-4017

Booster (<= 6.0.0), Booster Plus (<= 6.0.0), and Booster Elite (<= 6.0.0) for WooCommerce - Cross-Site Request Forgery

2023-01-02 00:00
WPScanTeam

Strategic Overview

Status
Patched in 6.0.1
Affected Plugin
Booster for WooCommerce – PDF Invoices, Abandoned Cart, Variation Swatches & 100+ Tools
Affected Version
<= 6.0.0
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-4017
View all Booster for WooCommerce – PDF Invoices, Abandoned Cart, Variation Swatches & 100+ Tools vulnerabilities

At a glance

CVE-2022-4017 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Booster for WooCommerce WordPress plugin, affecting versions <= 6.0.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.0.1; sites on affected versions should update now. Disclosed January 2023, reported by WPScanTeam.

Vulnerability Overview

The Booster plugins (Booster, Booster Plus, and Booster Elite) for WordPress are vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.0.0 (Booster), 6.0.0 (Plus), and 6.0.0 (Elite). This is due to missing or incorrect nonce validation on several functions. This makes it possible for unauthenticated attackers to invoke those functions 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.

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

Reaching this weakness in Booster for WooCommerce <= 6.0.0 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 Booster for WooCommerce the fix is 6.0.1: builds <= 6.0.0 are affected, anything from 6.0.1 onward is not.

Remediation

Update to version 6.0.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-4017https://www.wordfence.com/threat-intel/vulnerabilities/id/0af6e55d-def9-4bb1-ade9-56aa8184961chttps://nvd.nist.gov/vuln/detail/CVE-2022-4017

Related records

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