Content No Cache: prevent specific content from being cached <= 0.1.2 - Unauthenticated Private Content Disclosure
Strategic Overview
- Status
- Patched in 0.1.3
- Affected Plugin
- Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.
- Affected Version
<= 0.1.2- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-12103
At a glance
CVE-2024-12103 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Content No Cache WordPress plugin, affecting versions <= 0.1.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.1.3; sites on affected versions should update now. Disclosed December 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Content No Cache: prevent specific content from being cached plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 0.1.2 via the eos_dyn_get_content action due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Content No Cache <= 0.1.2 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Content No Cache the fix is 0.1.3: builds <= 0.1.2 are affected, anything from 0.1.3 onward is not.
Remediation
Update to version 0.1.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Content No Cache 0.1.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C