CVE-2022-4016

Booster (<= 5.6.6), Booster Plus (<= 5.6.5), and Booster Elite (<= 1.1.7) for WooCommerce - Cross-Site Request Forgery leading to Arbitrary Custom Role Creation/Deletion

2022-11-21 00:00
WPScanTeam

Strategic Overview

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

At a glance

CVE-2022-4016 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Booster for WooCommerce WordPress plugin, affecting versions <= 5.6.6. 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 5.6.7; sites on affected versions should update now. Disclosed November 2022, 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, 5.6.6 (Booster), 5.6.5 (Plus), and 1.1.7 (Elite). This is due to missing or incorrect nonce validation on functions such as 'process_actions' and 'get_delete_all_custom_statuses_button'. This makes it possible for unauthenticated attackers to create and delete arbitrary custom roles 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)

Booster for WooCommerce <= 5.6.6 carries this weakness at process_actions, 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 Booster for WooCommerce the fix is 5.6.7: builds <= 5.6.6 are affected, anything from 5.6.7 onward is not.

Remediation

Update to version 5.6.7, 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 5.6.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-4016https://www.wordfence.com/threat-intel/vulnerabilities/id/21cc3f71-7591-4111-a58a-d863df74587fhttps://nvd.nist.gov/vuln/detail/CVE-2022-4016

Related records

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