String Locator <= 2.6.6 - Unauthenticated PHP Object Injection
Strategic Overview
- Status
- Patched in 2.6.7
- Affected Plugin
- String locator
- Affected Version
<= 2.6.6- CVSS
- 8.8High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2024-10936
At a glance
CVE-2024-10936 is a high-severity Deserialization of Untrusted Data vulnerability in the String locator WordPress plugin, affecting versions <= 2.6.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.6.7; sites on affected versions should update now. Disclosed January 2025, reported by Webbernaut.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
String locator <= 2.6.6 carries this weakness at recursive_unserialize_replace, and reaching it takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For String locator the fix is 2.6.7: builds <= 2.6.6 are affected, anything from 2.6.7 onward is not.
Remediation
Update to version 2.6.7, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: String locator 2.6.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C