CVE-2024-10936·PHP vulnerability
The String locator plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.6.6 via deserialization of untrusted input in the 'recursive_unserialize_replace' function. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code. An administrator must perform a search and replace action to trigger the exploit.
- Severity
- high
- Software
- PHP
- Fixed in
- 2.6.7
- Published
- 2025-01-21
Affected versions
Until: 2.6.7
Fixed in: 2.6.7
How to fix this CVE
Update the String Locator WordPress plugin to version 2.6.7 or later to patch the PHP Object Injection vulnerability in the deserialization function. If you cannot immediately update, disable the plugin and remove it from your WordPress installation until a patch is deployed. This vulnerability requires administrator interaction to trigger, so review recent search and replace activity in your WordPress admin logs.
sudo dnf check-update php && sudo dnf upgrade phpDefensia detects this vulnerability
How to check if you are affected
- Check the installed PHP version: php -v
- Verify the String Locator plugin version in WordPress by navigating to Plugins > Installed Plugins and locating 'String Locator'; note the version number displayed
- Search WordPress logs at wp-content/debug.log for entries containing 'unserialize' or 'recursive_unserialize_replace' executed around the time suspicious search-replace activity occurred
- After updating, re-run the plugin version check to confirm version 2.6.7 or later is installed: grep -r 'Version:' wp-content/plugins/string-locator/string-locator.php | head -1
FAQ
What is CVE-2024-10936?
CVE-2024-10936 is a PHP Object Injection flaw in the String Locator WordPress plugin that occurs when the plugin deserializes untrusted user input without proper validation. An attacker could inject malicious PHP objects that, when combined with vulnerable code in other plugins or themes, may lead to file deletion, data theft, or code execution.
Is CVE-2024-10936 being actively exploited?
No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, the lack of a public exploit does not eliminate the risk if malicious actors develop one.
What versions of the String Locator plugin are affected by CVE-2024-10936?
All versions of the String Locator plugin up to and including 2.6.6 are affected. Version 2.6.7 and later contain the fix.
How do I check if my WordPress site is vulnerable to CVE-2024-10936?
Log in to your WordPress admin panel, go to Plugins > Installed Plugins, find 'String Locator', and check if the version number is 2.6.6 or lower. If so, your site is vulnerable.
Does Defensia detect CVE-2024-10936?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the String Locator plugin is detected on a monitored WordPress server, CVE-2024-10936 will appear in your dashboard with remediation steps.
Related PHP CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-10936. Free for 1 server.
Get started free