Skip to content

CVE-2024-12103 Content No Cache: prevent specific content from being cached <= 0.1.2 - Unauthenticated Private Content Disclosure

MediumCVSS 5.3 EPSS 0.40%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: yes · technical impact: partial
Technology
WordPress

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.

Upgrade path

2 packages: 2 fixed.

PackageAffectedFixed inStatus
giuse Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached. <= 0.1.2 after 0.1.2 Fixed
wordpress content-no-cache(WordPress) < 0.1.3 0.1.3 Fixed

Affected products

ProductAffected versionsFixed in
giuse Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached. <= 0.1.2 No fix listed
wordpress content-no-cache(WordPress) < 0.1.3 0.1.3

References