CVE-2023-5359: The W3 Total Cache plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and

Q: How do I fix CVE-2023-5359?

w3 total cache: upgrade to 2.7.6. Exact commands for each OS are on this page.

Q: Is CVE-2023-5359 being exploited?

CVE-2023-5359 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2023-5359 affect?

CVE-2023-5359 affects w3 total cache. Severity is low (CVSS 3.7). 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 unauthent

Q: How urgent is CVE-2023-5359?

Priority 32/100. Remotely exploitable, no login, no user action

Routine

LOW 3.7REMOTEUPGRADE

CVE-2023-5359 is a low-severity flaw (CVSS 3.7) affecting w3 total cache. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	3.7 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.8% (top 43%)
CISA exploited list	No
Weakness	CWE-200, CWE-312
Published	2024-09-25
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: boldgrid

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-09-25 01:15 UTCPublished CVE record published
2026-06-17 06:48 UTCUpdated Record last modified

boldgrid w3 total cache UPGRADE

Affected: < 2.7.6

Fixed in: 2.7.6

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy w3-total-cache || rpm -q w3-total-cache || w3-total-cache --version

2. UPGRADE to 2.7.6 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade w3-total-cache

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade w3-total-cache

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-5359?

w3 total cache: upgrade to 2.7.6. Exact commands for each OS are on this page.

Is CVE-2023-5359 being exploited?

CVE-2023-5359 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-5359 affect?

CVE-2023-5359 affects w3 total cache. Severity is low (CVSS 3.7). 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 unauthent

How urgent is CVE-2023-5359?

Priority 32/100. Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-12365 HIGH 8.5 UPGRADE The W3 Total Cache plugin for WordPress is vulnerable to unauthorized access of data due to a missing capabili
CVE-2024-12008 MEDIUM 5.3 UPGRADE The W3 Total Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to, and inclu
CVE-2024-12006 MEDIUM 5.3 UPGRADE The W3 Total Cache plugin for WordPress is vulnerable to unauthorized modification of data due to a missing ca

References

← Back to latest CVEs