CVE-2023-5359

W3 Total Cache <= 2.7.5 - Sensitive Credentials Stored in Plaintext

2024-09-23 00:00
Ivan Kuzymchak

Strategic Overview

Status
Patched in 2.7.6
Affected Plugin
W3 Total Cache
Affected Version
<= 2.7.5
CVSS
3.7Low
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2023-5359
View all W3 Total Cache vulnerabilities

At a glance

CVE-2023-5359 is a low-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the W3 Total Cache WordPress plugin, affecting versions <= 2.7.5. It carries a CVSS score of 3.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 2.7.6; sites on affected versions should update now. Disclosed September 2024, reported by Ivan Kuzymchak.

Vulnerability Overview

The W3 Total Cache plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.7.5 via Google OAuth API secrets stored in plaintext in the publicly visible plugin source. This can allow unauthenticated attackers to impersonate W3 Total Cache and gain access to user account information in successful conditions. This would not impact the WordPress users site in any way.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in W3 Total Cache <= 2.7.5 takes a caller who can reach the endpoint. 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 W3 Total Cache the fix is 2.7.6: builds <= 2.7.5 are affected, anything from 2.7.6 onward is not.

Remediation

Update to version 2.7.6, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: W3 Total Cache 2.7.6 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