Skip to main content
CVE-2024-12103VulnerabilityPublished Updated

CVE-2024-12103: Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached. (WordPress plugin) · Insecure Direct Object Reference

Affects Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached. (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
giuse Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.Affected
  • =0
Fixed in–

AI-suggested

Until a fix is available, users should consider disabling the Content No Cache plugin or restricting access to the affected functionality to trusted users only. Monitor official giuse or WordPress plugin repositories for updates addressing this vulnerability.

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.

References

Community reviews

Loading reviews…