String locator vulnerabilities
Plugin slug string-locator · 5 known vulnerabilities · latest disclosed 2026-10-05 · WordPress.org page
Every listed vulnerability has a fix. Version 2.6.8 or later is not affected by any of them. If your site runs an older version, update it.
3 of 5 rated high or critical (CVSS 7 or more).
Known vulnerabilities in String locator
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| High 8.1 | <= 2.6.7 | 2.6.8 | CVE-2026-97188 | 2026-10-05 | Advisory |
| High 8.8 | <= 2.6.6 | 2.6.7 | CVE-2024-10936 | 2025-01-20 | Advisory |
| Medium 6.1 | <= 2.6.5 | 2.6.6 | CVE-2023-6987 | 2024-08-23 | Advisory |
| High 8.8 | <= 2.5.0 | 2.6.0 | CVE-2022-2434 | 2022-08-08 | Advisory |
| Medium 4.9 | < 2.5.0 | 2.5.0 | CVE-2022-0493 | 2022-03-01 | Advisory |
Check if a site is affected
Enter a site address to see which version of String locator and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the String locator plugin safe to use?
All 5 known issues are fixed in current versions (2.6.8 or later). Keeping it updated is what matters.
How do I check which version of String locator my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.