CVE-2023-40002

Booster for WooCommerce <= 7.1.1 - Authenticated (Subscriber+) Information Disclosure via Shortcode

2023-10-04 00:00
Dave Jong

Strategic Overview

Status
Patched in 7.1.2
Affected Version
<= 7.1.1
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2023-40002
View all Booster for WooCommerce – PDF Invoices, Abandoned Cart, Variation Swatches & 100+ Tools vulnerabilities

At a glance

CVE-2023-40002 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Booster for WooCommerce WordPress plugin, affecting versions <= 7.1.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 7.1.2; sites on affected versions should update now. Disclosed October 2023, reported by Dave Jong.

Vulnerability Overview

The Booster for WooCommerce for WordPress is vulnerable to Information Disclosure via the 'wcj_get_option' shortcode in versions up to, and including, 7.1.1 due to insufficient controls on the information retrievable via the shortcode. This makes it possible for authenticated attackers, with subscriber-level capabilities or above, to retrieve arbitrary sensitive site options.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Booster for WooCommerce <= 7.1.1 carries this weakness at wcj_get_option, and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Booster for WooCommerce the fix is 7.1.2: builds <= 7.1.1 are affected, anything from 7.1.2 onward is not.

Remediation

Update to version 7.1.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Booster for WooCommerce 7.1.2 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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