CVE-2024-31094
📋 TL;DR
This CVE describes a PHP object injection vulnerability in the WordPress Filter Custom Fields & Taxonomies Light plugin. Attackers can exploit insecure deserialization to execute arbitrary code on affected WordPress sites. All WordPress installations using vulnerable versions of this plugin are affected.
💻 Affected Systems
- WordPress Filter Custom Fields & Taxonomies Light plugin
⚠️ 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.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Remote code execution leading to complete system compromise, data theft, website defacement, or installation of persistent backdoors.
Likely Case
Arbitrary code execution allowing attackers to create administrator accounts, modify content, or install malware.
If Mitigated
Limited impact if proper web application firewalls and input validation are in place.
🎯 Exploit Status
Public exploit details are available, making this easily exploitable by attackers with basic skills.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 1.06 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'Filter Custom Fields & Taxonomies Light'. 4. Click 'Update Now' if update is available. 5. If no update appears, manually download version 1.06+ from WordPress repository and replace plugin files.
🔧 Temporary Workarounds
Disable vulnerable plugin
allTemporarily deactivate the plugin until patched
wp plugin deactivate filter-custom-fields-taxonomies-light
Web Application Firewall rule
allBlock requests containing serialized PHP objects
ModSecurity rule: SecRule ARGS "@rx O:[0-9]+:" "id:1001,phase:2,deny,msg:'PHP Object Injection Attempt'"
WAF configuration to block suspicious POST requests to plugin endpoints
🧯 If You Can't Patch
- Remove the plugin entirely from production environment
- Implement strict network segmentation and limit access to affected WordPress instances
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel → Plugins → Filter Custom Fields & Taxonomies Light → Version. If version is 1.05 or lower, you are vulnerable.Check Version:
wp plugin get filter-custom-fields-taxonomies-light --field=versionVerify Fix Applied:
After update, verify plugin version shows 1.06 or higher in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to plugin endpoints
- PHP errors related to unserialize() function
- Unexpected file creation in wp-content/uploads
Network Indicators:
- HTTP requests containing serialized PHP objects (O:8:"stdClass":)
- Traffic to known exploit patterns for this CVE
SIEM Query:
source="wordpress.log" AND ("filter-custom-fields-taxonomies-light" OR "unserialize") AND status=200🔗 References
- https://patchstack.com/database/vulnerability/filter-custom-fields-taxonomies-light/wordpress-filter-custom-fields-taxonomies-light-plugin-1-05-php-object-injection-vulnerability?_s_id=cve
- https://patchstack.com/database/vulnerability/filter-custom-fields-taxonomies-light/wordpress-filter-custom-fields-taxonomies-light-plugin-1-05-php-object-injection-vulnerability?_s_id=cve
