CVE-2024-10871

9.8 CRITICAL

📋 TL;DR

The Category Ajax Filter WordPress plugin has a Local File Inclusion vulnerability that allows unauthenticated attackers to include and execute arbitrary PHP files on the server. This can lead to remote code execution, data theft, and complete system compromise. All WordPress sites using this plugin up to version 2.8.2 are affected.

💻 Affected Systems

Products:
  • WordPress Category Ajax Filter plugin
Versions: All versions up to and including 2.8.2
Operating Systems: All operating systems running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with the vulnerable plugin activated. No authentication required for exploitation.

⚠️ 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

Complete server takeover via remote code execution, data exfiltration, backdoor installation, and lateral movement to other systems.

🟠

Likely Case

Website defacement, credential theft, database compromise, and installation of cryptocurrency miners or malware.

🟢

If Mitigated

Limited impact if file uploads are restricted, PHP execution is disabled in upload directories, and proper file permissions are enforced.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation is straightforward via HTTP requests to the vulnerable parameter. Public proof-of-concept code is available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.8.3

Vendor Advisory: https://plugins.trac.wordpress.org/changeset/3183800/

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'Category Ajax Filter' and update to version 2.8.3 or later. 4. Alternatively, deactivate and delete the plugin if not needed.

🔧 Temporary Workarounds

Disable vulnerable plugin

all

Deactivate the Category Ajax Filter plugin immediately

wp plugin deactivate category-ajax-filter

Web Application Firewall rule

all

Block requests containing the malicious parameter pattern

Add WAF rule to block: params[caf-post-layout] with file path traversal patterns

🧯 If You Can't Patch

  • Disable the Category Ajax Filter plugin immediately
  • Implement strict file upload restrictions and disable PHP execution in upload directories

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel → Plugins → Category Ajax Filter version. If version is 2.8.2 or lower, you are vulnerable.

Check Version:

wp plugin get category-ajax-filter --field=version

Verify Fix Applied:

Verify plugin version is 2.8.3 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • HTTP requests containing 'params[caf-post-layout]' with file path traversal patterns
  • Unexpected PHP file inclusions in web server logs
  • Multiple failed inclusion attempts

Network Indicators:

  • HTTP GET/POST requests to WordPress with suspicious file paths in parameters
  • Traffic spikes to plugin-specific endpoints

SIEM Query:

source="web_server" AND ("params[caf-post-layout]" OR "caf-post-layout") AND (".." OR "/etc/" OR "/proc/")

🔗 References

📤 Share & Export