Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-12447: CWE-639 Authorization Bypass Through User-Controlled Key in webdeveric Get Post Content Shortcode

0
Medium
VulnerabilityCVE-2024-12447cvecve-2024-12447cwe-639
Published: Sat Dec 14 2024 (12/14/2024, 04:23:45 UTC)
Source: CVE Database V5
Vendor/Project: webdeveric
Product: Get Post Content Shortcode

Description

CVE-2024-12447 is a medium severity vulnerability in the WordPress plugin Get Post Content Shortcode by webdeveric. It allows authenticated users with Contributor-level access or higher to bypass authorization controls via an insecure direct object reference (IDOR) vulnerability. This occurs because the plugin fails to validate a user-controlled key parameter in the 'post-content' shortcode, enabling unauthorized reading of password-protected, private, draft, and pending posts. Exploitation requires no user interaction beyond authentication and can lead to confidentiality breaches of sensitive content. The vulnerability affects all versions up to 0. 4 of the plugin. No known exploits are currently in the wild, and no patches have been released yet. Organizations using this plugin should restrict contributor access and monitor for suspicious activity until a fix is available.

AI-Powered Analysis

AILast updated: 02/26/2026, 04:43:18 UTC

Technical Analysis

CVE-2024-12447 is an authorization bypass vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) found in the Get Post Content Shortcode WordPress plugin developed by webdeveric. The flaw exists in all versions up to and including 0.4 and stems from the plugin's failure to validate a user-controlled key parameter passed to the 'post-content' shortcode. This missing validation allows authenticated users with Contributor-level permissions or higher to exploit an insecure direct object reference (IDOR) vulnerability. By manipulating the shortcode parameter, attackers can access the content of posts that are normally restricted, including password-protected, private, draft, and pending posts. The vulnerability does not require user interaction beyond authentication and can be exploited remotely over the network. The CVSS v3.1 base score is 4.3 (medium severity), reflecting low impact on confidentiality (limited to reading content), no impact on integrity or availability, low attack complexity, and requiring privileges (Contributor or higher). No patches or known exploits have been reported as of the publication date. This vulnerability poses a risk to WordPress sites using this plugin, especially those with multiple contributors or less restrictive user role assignments.

Potential Impact

The primary impact of CVE-2024-12447 is unauthorized disclosure of sensitive post content within affected WordPress sites. Attackers with Contributor-level access can read posts that are intended to be private, password-protected, drafts, or pending review, potentially exposing confidential business information, unpublished content, or other sensitive data. This breach of confidentiality can lead to reputational damage, intellectual property loss, and privacy violations. Since the vulnerability does not affect integrity or availability, it does not allow content modification or denial of service. However, the ease of exploitation by authenticated users means insider threats or compromised contributor accounts can be leveraged to escalate data exposure. Organizations with collaborative content workflows or external contributors are at higher risk. The lack of a patch increases the window of exposure until a fix is released. Overall, the vulnerability undermines trust in content access controls within affected WordPress environments.

Mitigation Recommendations

To mitigate CVE-2024-12447, organizations should immediately audit and restrict Contributor-level and higher user permissions to trusted individuals only, minimizing the risk of insider exploitation. Temporarily disabling or removing the Get Post Content Shortcode plugin until a patch is available can eliminate the attack vector. If plugin removal is not feasible, implement custom access controls or filters to validate and sanitize shortcode parameters, ensuring unauthorized users cannot manipulate keys to access restricted posts. Monitoring logs for unusual shortcode usage or access patterns can help detect exploitation attempts. Additionally, site administrators should enforce strong authentication mechanisms and consider multi-factor authentication to reduce the risk of compromised contributor accounts. Stay informed on vendor updates and apply patches promptly once released. Finally, review and tighten WordPress user role assignments and content visibility settings to limit exposure.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-12-10T19:11:51.611Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e3bb7ef31ef0b598a84

Added to database: 2/25/2026, 9:48:43 PM

Last enriched: 2/26/2026, 4:43:18 AM

Last updated: 2/26/2026, 7:50:05 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats