Content No Cache | Serve Uncached Partial Content Even When You Add It To A Page That Is Fully Cached.
Approved changes feed: RSS · Atom
cpe:2.3:a:giuse:content_no_cache_|_serve_uncached_partial_content_even_when_you_add_it_to_a_page_that_is_fully_cached.:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Giuse (2938f4ab-30f7-536d-afee-0bd7463e79db) |
|---|---|
| Product | Content No Cache | Serve Uncached Partial Content Even When You Add It To A Page That Is Fully Cached. (dfbe5a03-1462-58ee-83ed-980c1f509bb1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-12103 |
vulnerable | 2026-06-08 06:23:51.267718 |
Content No Cache: prevent specific content from being cached <= 0.1.2 - Unauthenticated Private Content Disclosure
MEDIUM (5.3)
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.
Published: 2024-12-24T09:21:50.231Z
Updated: 2026-04-08T17:06:49.750Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.