CVE-2024-12103

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

State
Published
Severity
5.3 Medium
Published
Dec 24, 2024
Updated
Apr 8, 2026
Reserved
Dec 3, 2024

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.15.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NWordfence

Weaknesses

  • CWE-639 Authorization Bypass Through User-Controlled Key

Affected Products

ProductVersions
Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.giuse
  • 0.1.2 and earlierAffected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.