CVE-2023-5359
3.7 · LOWOverview
CVE-2023-5359 is a low-severity vulnerability affecting boldgrid w3_total_cache. It was published on September 25, 2024 and has a CVSS 3.1 base score of 3.7 (LOW).
This vulnerability has a CVSS 3.1 base score of 3.7, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical Description
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.
Remediation
Check the references section for vendor advisories and patches from boldgrid. Update w3_total_cache to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| boldgrid | w3_total_cache | >= 0, < 2.7.6 | Affected |
Frequently Asked Questions
What is CVE-2023-5359?
CVE-2023-5359 is a low-severity vulnerability affecting boldgrid w3_total_cache. It was published on September 25, 2024 and has a CVSS 3.1 base score of 3.7 (LOW).
How severe is CVE-2023-5359?
This vulnerability has a CVSS 3.1 base score of 3.7, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2023-5359?
Check the references section for vendor advisories and patches from boldgrid. Update w3_total_cache to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2023-5359?
CyberStrike's AI-powered security agents can automatically detect CVE-2023-5359 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related LOW CVEs from 2023
View all →A CWE-668: Exposure of Resource to Wrong Sphere vulnerability exists that could cause all remote dom
All versions of Landis+Gyr E850 (ZMQ200) are vulnerable to CWE-784: Reliance on Cookies Without Vali
Dell PowerEdge BIOS and Dell Precision BIOS contain an improper input validation vulnerability. A
A vulnerability was found in Deye/Revolt/Bosswerk Inverter MW3_15U_5406_1.47/MW3_15U_5406_1.471. It
Azure/setup-kubectl is a GitHub Action for installing Kubectl. This vulnerability only impacts versi
IBM Robotic Process Automation 21.0.1 through 21.0.7 and 23.0.0 through 23.0.1 could allow a user wi
This vulnerability allows local attackers to execute arbitrary code on affected installations of Sam
Kiwi TCMS is an open source test management system. In versions of Kiwi TCMS prior to 12.2, users we
Wasmtime is a standalone runtime for WebAssembly. Prior to versions 6.0.2, 7.0.1, and 8.0.1, Wasmtim
Insufficient input validation in the SMU may allow an attacker to corrupt SMU SRAM potentially leadi
Out-of-bounds write for some Intel(R) Trace Analyzer and Collector software before version 2021.8.0
Libarchive through 3.6.2 can cause directories to have world-writable permissions. The umask() call