CVE-2023-4242

FULL - Customer <= 2.2.3 - Authenticated(Subscriber+) Information Disclosure via Health Check

2023-08-08 00:00
Ram

Strategic Overview

Status
Patched in 2.3
Affected Plugin
FULL – Cliente
Affected Version
<= 2.2.3
CVSS
4.3Medium
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2023-4242
View all FULL – Cliente vulnerabilities

At a glance

CVE-2023-4242 is a medium-severity Improper Authentication vulnerability in the FULL WordPress plugin, affecting versions <= 2.2.3. 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 2.3; sites on affected versions should update now. Disclosed August 2023, reported by Ram.

Vulnerability Overview

The FULL - Customer plugin for WordPress is vulnerable to Information Disclosure via the /health REST route in versions up to, and including, 2.2.3 due to improper authorization. This allows authenticated attackers with subscriber-level permissions and above to obtain sensitive information about the site configuration as disclosed by the WordPress health check.

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-287: Improper Authentication

Reaching this weakness in FULL <= 2.2.3 takes an account at Subscriber level or above. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For FULL the fix is 2.3: builds <= 2.2.3 are affected, anything from 2.3 onward is not.

Remediation

Update to version 2.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: FULL 2.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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