Vulnerability · Published Dec 24, 2024 · Assigned by Wordfence
CVE-2024-12103Content No Cache: prevent specific content from being cached <= 0.1.2 - Unauthenticated Private Content Disclosure
Medium 5.3
In plain English
A medium-severity authorization bypass via user-controlled key in Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached. from giuse. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 35% of all known vulnerabilities).
Official description
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.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| giuse | Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached. | 0 – through 0.1.2 |
Weakness: CWE-639 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N