CVE-2024-12103 Content No Cache: prevent specific content from being cached <= 0.1.2 - Unauthenticated Private Content Disclosure
Unauthenticated attackers can extract data from password protected, private, or draft posts via insufficient restrictions in the Content No Cache plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-12103?
CVE-2024-12103 is a medium-severity vulnerability in giuse Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached., published on 24 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
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.
Weakness: CWE-639
Which versions are affected by CVE-2024-12103?
How do I fix CVE-2024-12103?
No fix has been published for CVE-2024-12103 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-12103 being exploited?
There is no known exploitation of CVE-2024-12103 in the wild and no public exploit code.
Sources
Also known as GHSA-8v57-2x2q-jr9m.