CVE-2024-12103
Content No Cache: prevent specific content from being cached <= 0.1.2 - Unauthenticated Private Content Disclosure
Vexday Risk Score
13Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS 5.3EPSS 0.4%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
24 Dec 2024Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected products
giuse · Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.Want to know if your infrastructure is exposed to this?
Talk to TrueHacking →