CVE-2024-12103
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WordPress 'Content No Cache' plugin has an information exposure vulnerability in the eos_dyn_get_content action. Due to insufficient authorization checks, unauthenticated attackers can retrieve content from password-protected, private, or draft posts that should be restricted.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Content No Cache plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'content-no-cache' or similar, or list active plugins via WordPress admin or databaseAffected if Plugin folder exists in wp-content/plugins/ and plugin is active
-
Identify installed plugin versionOpen the main plugin PHP file (typically content-no-cache.php) and locate the Version header in the plugin comment block, or check readme.txtAffected if Version is present but is lower than 0.1.3
-
Check if AJAX action endpoint is accessibleTest access to the vulnerable endpoint: make a request to wp-admin/admin-ajax.php with action=eos_dyn_get_content (no authentication required)Affected if Endpoint returns content from password-protected, private, or draft posts without providing credentials
-
Confirm vulnerable plugin configurationReview plugin settings in WordPress admin under the plugin settings page, if any, to confirm the dynamic content feature is enabledAffected if Plugin is configured and the eos_dyn_get_content action responds to requests
A user is affected if the Content No Cache plugin is active with a version lower than 0.1.3 and the eos_dyn_get_content AJAX action is accessible without authentication, allowing retrieval of restricted post content
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to version 0.1.3 or later which implements proper authorization checks; alternatively, disable the plugin until a patched version is available.
Plugin version 0.1.3 or latest available version
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Content No Cache' (or 'Content No Cache: prevent specific content from being cached') plugin
- Click 'Update Now' if an update is available, or manually update to the latest version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-12103 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data