HomeWordPress vulnerabilitiesString locator
String locator vulnerabilities
String locator has 5 known vulnerabilities in this database. The most recent published record is dated 7 Oct 2026.
- Known vulnerabilities
- 5
- Active installs
- 100,000+
- Latest version
- 2.6.8
- Last updated
- 29 Sep 2026
- Most recent
- 7 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-97188 | High 8.8 | Before 2.6.8 | Fixed in 2.6.8 | 18 h ago |
| PHP object injection CVE-2024-10936 | High 8.8 | Before 2.6.7 | Fixed in 2.6.7 | 21 Jan 2025 |
| Cross-site scripting (XSS) CVE-2023-6987 | Medium 6.1 | Before 2.6.6 | Fixed in 2.6.6 | 24 Aug 2024 |
| PHP object injection CVE-2022-2434 | High 8.8 | Up to 2.5.0 | Fixed in a later version (latest 2.6.8) | 6 Sep 2022 |
| Path traversal CVE-2022-0493 | Medium 4.9 | Before 2.5.0 | Fixed in 2.5.0 | 28 Mar 2022 |
Read the published descriptions
- CVE-2026-97188, 7 Oct 2026
- The String locator WordPress plugin before 2.6.8 does not restrict the classes allowed when deserializing the content of a database row saved through its database editor, allowing unauthenticated attackers to store a serialized PHP object that is instantiated when an administrator later opens and saves that row. If a suitable POP chain is present via another installed String locator WordPress plugin before 2.6.8 or , this can lead to arbitrary file deletion, sensitive data disclosure or remote code execution. CVE record
- CVE-2024-10936, 21 Jan 2025
- 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. CVE record
- CVE-2023-6987, 24 Aug 2024
- The String locator plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'sql-column' parameter in all versions up to, and including, 2.6.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. This required WP_DEBUG to be enabled in order to be exploited. CVE record
- CVE-2022-2434, 6 Sep 2022
- The String Locator plugin for WordPress is vulnerable to deserialization of untrusted input via the 'string-locator-path' parameter in versions up to, and including 2.5.0. This makes it possible for unauthenticated users to call files using a PHAR wrapper, granted they can trick a site administrator into performing an action such as clicking on a link, that will deserialize and call arbitrary PHP Objects that can be used to perform a variety of malicious actions granted a POP chain is also present. It also requires that the attacker is successful in uploading a file with the serialized payload. CVE record
- CVE-2022-0493, 28 Mar 2022
- The String locator WordPress plugin before 2.5.0 does not properly validate the path of the files to be searched, allowing high privilege users such as admin to query arbitrary files on the web server via a path traversal vector. Furthermore, due to a flaw in the search, allowing a pattern to be provided, which will be used to output the relevant matches from the matching file, all content of the file can be disclosed. CVE record
What to do if you run String locator
If you run String locator, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new String locator vulnerabilities
Free. We email you when a new vulnerability is published for String locator, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.