VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2024-12103Published · Updated

Action summary

Affected: ≤0.1.2Update to 0.1.3 or newer

All remediation steps
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:N Integrity
None
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached. content-no-cache

  1. Affected≤ 0.1.2
  2. Patched in0.1.3

Update to 0.1.3 or newer.

You are affected if you run ≤ 0.1.2. Version 0.1.3 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached..
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 0.1.3, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached. to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Francesco Carlucci.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.

All 2
More vulnerabilities in Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.
SeverityVulnerabilityCVEPublished
High7.3Unauthenticated Arbitrary Function Call
≤0.1.4Update to 0.1.5
CVE-2025-28993

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?