CVE-2024-12103: CWE-639 Authorization Bypass Through User-Controlled Key in giuse Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.
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.
AI Analysis
Technical Summary
CVE-2024-12103 affects the Content No Cache WordPress plugin by allowing unauthorized information exposure. The vulnerability arises because the plugin does not properly restrict access to certain post types when processing the eos_dyn_get_content action, enabling unauthenticated users to retrieve content from posts that should be protected, such as password protected, private, or draft posts. This results in an authorization bypass (CWE-639) leading to unintended data disclosure. The issue impacts all plugin versions up to and including 0.1.2. No official patch or vendor advisory is currently available.
Potential Impact
An attacker without authentication can extract sensitive content from posts that are intended to be restricted, including password protected, private, or draft posts. This leads to unauthorized information disclosure but does not affect integrity or availability. The CVSS score of 5.3 reflects a medium severity impact focused on confidentiality loss.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. 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.
CVE-2024-12103: CWE-639 Authorization Bypass Through User-Controlled Key in giuse Content No Cache | Serve uncached partial content even when you add it to a page that is fully cached.
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-12103 affects the Content No Cache WordPress plugin by allowing unauthorized information exposure. The vulnerability arises because the plugin does not properly restrict access to certain post types when processing the eos_dyn_get_content action, enabling unauthenticated users to retrieve content from posts that should be protected, such as password protected, private, or draft posts. This results in an authorization bypass (CWE-639) leading to unintended data disclosure. The issue impacts all plugin versions up to and including 0.1.2. No official patch or vendor advisory is currently available.
Potential Impact
An attacker without authentication can extract sensitive content from posts that are intended to be restricted, including password protected, private, or draft posts. This leads to unauthorized information disclosure but does not affect integrity or availability. The CVSS score of 5.3 reflects a medium severity impact focused on confidentiality loss.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. 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.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2024-12-03T15:16:42.216Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6e2db7ef31ef0b5974d7
Added to database: 2/25/2026, 9:48:29 PM
Last enriched: 4/9/2026, 12:35:54 PM
Last updated: 4/11/2026, 9:21:27 PM
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.