CVE-2023-5359: w3 total cache vulnerability

CVE-2023-5359: low vulnerability affecting w3 total cache. Check CVSS, KEV status, business impact and recommended administrator actions.
CVE-2023-5359CVSS 3.7Web

CVE-2023-5359: w3 total cache vulnerability

CVE-2023-5359: low vulnerability affecting w3 total cache. Check CVSS, KEV status, business impact and recommended administrator actions.

CVSS
3.7 LOW
EPSS
53.24%
Known exploited
not in KEV
Product
w3 total cache

What is known

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.

Business impact

Successful exploitation of CVE-2023-5359, a low vulnerability (CVSS 3.7) affecting w3 total cache, may affect the confidentiality, integrity or availability of the vulnerable environment. The exact impact depends on the installed version, exposed interfaces and deployment configuration.

Recommended administrator action

Confirm whether w3 total cache is present and compare installed versions with the vendor advisory and NVD record. Apply the vendor patch or documented mitigation; until remediation is complete, reduce exposure of affected interfaces, review relevant logs and monitor for indicators of exploitation. DataHouse can support version verification, managed patching, network exposure reduction, log review and backup validation for dedicated, cloud and colocated environments.

Sources

Security newsletter

Get new CVE alerts before they become an incident

We send selected infrastructure threats in English, with practical notes for DataHouse environments.

  • DataHouse: server administration and secure cloud
  • Hostilla.pl: hosting and mail services
  • SecDNS.pl: free DNS security layer