CVE-2024-12103

5.3 MEDIUM

📋 TL;DR

This vulnerability in the WordPress Content No Cache plugin allows unauthenticated attackers to access password-protected, private, or draft posts that should be restricted. All WordPress sites using this plugin up to version 0.1.2 are affected. Attackers can extract sensitive content they shouldn't have permission to view.

💻 Affected Systems

Products:
  • WordPress Content No Cache plugin
Versions: All versions up to and including 0.1.2
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects WordPress installations with the vulnerable plugin active. The vulnerability exists in the eos_dyn_get_content action handler.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Sensitive unpublished content, confidential drafts, or password-protected information is exposed to the public internet, potentially leading to data breaches, intellectual property theft, or reputational damage.

🟠

Likely Case

Attackers discover and extract draft posts, private content, or password-protected materials that were intended to be restricted, compromising content confidentiality.

🟢

If Mitigated

With proper access controls and monitoring, exposure is limited to specific content types rather than full system compromise, but confidentiality is still breached.

🌐 Internet-Facing: HIGH
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires sending crafted requests to the vulnerable endpoint. No authentication is needed, making this easily exploitable.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 0.1.3 or later

Vendor Advisory: https://plugins.trac.wordpress.org/changeset/3211815/content-no-cache/trunk/inc/eos-dyn-ajax.php

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins. 3. Find 'Content No Cache' plugin. 4. Click 'Update Now' if update is available. 5. Alternatively, download version 0.1.3+ from WordPress plugin repository and manually update.

🔧 Temporary Workarounds

Disable vulnerable plugin

all

Temporarily deactivate the Content No Cache plugin until patched

wp plugin deactivate content-no-cache

Restrict access to wp-admin/admin-ajax.php

linux

Limit access to the vulnerable endpoint via web server configuration

# Add to .htaccess for Apache:
<Files "admin-ajax.php">
Order Deny,Allow
Deny from all
Allow from 127.0.0.1
</Files>
# Add to nginx config:
location ~* /wp-admin/admin-ajax.php {
allow 127.0.0.1;
deny all;
}

🧯 If You Can't Patch

  • Deactivate the Content No Cache plugin immediately
  • Implement WAF rules to block requests to admin-ajax.php with eos_dyn_get_content action

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Content No Cache. If version is 0.1.2 or lower, you are vulnerable.

Check Version:

wp plugin get content-no-cache --field=version

Verify Fix Applied:

Verify plugin version is 0.1.3 or higher in WordPress admin panel. Test that password-protected/draft posts cannot be accessed via unauthenticated requests.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to /wp-admin/admin-ajax.php with action=eos_dyn_get_content
  • Access to draft/private posts from unauthenticated IPs
  • Multiple failed attempts to access restricted content

Network Indicators:

  • HTTP POST requests to admin-ajax.php with eos_dyn_get_content parameter from external IPs
  • Unusual traffic patterns to WordPress admin endpoints

SIEM Query:

source="web_logs" AND uri_path="/wp-admin/admin-ajax.php" AND http_method="POST" AND form_data.action="eos_dyn_get_content"

🔗 References

📤 Share & Export