CVE-2024-12008
W3 Total Cache <= 2.8.1 Information Exposure via Log Files
Record summary
CVE-2024-12008 has a selected CVSS score of 5.3 (medium); EIP currently links 1 repository PoC and 1 Nuclei template.
Description
The W3 Total Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.8.1 through the publicly exposed debug log file. This makes it possible for unauthenticated attackers to view potentially sensitive information in the exposed log file. For example, the log file may contain nonce values that can be used in further CSRF attacks. Note: the debug feature must be enabled for this to be a concern, and it is disabled by default.
Exploitation context
Affected products and versions
1| Product | Source | Version range | Status |
|---|---|---|---|
W3 Total CacheBrowse boldgrid / W3 Total CacheDefault status: unaffected | CVE List | Through 2.8.1 | affected |
Proofs of concept
1Repository PoCs
GitHubspyata123/CVE-2024-12008-information-exposure-vulnerability-in-W3-Total-CacheRepository PoCby spyata123Stars: 0Not analyzed2 files
Nuclei templates
1ProjectDiscoveryMEDIUMW3 Total Cache < 2.8.2 - Log File ExposureCVSS 5.3
The plugin is vulnerable to Information Exposure through the publicly exposed debug log file. This makes it possible for unauthenticated attackers to view potentially sensitive information in the exposed log file. For example, the log file may contain nonce values that can be used in further CSRF attacks.
Impact
Unauthenticated attackers can extract sensitive credentials, leading to potential account compromise and further attacks.
Remediation
Update the W3 Total Cache plugin to version 2.8.2 or later, which restricts access to debug log files. Additionally, disable debug logging in production environments and ensure .htaccess rules block direct access to the cache/log directory.
Source: ProjectDiscovery