WordPress plugin
String locator security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 5 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High3
- Medium2
- Low0
All String locator vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.1 | Unauthenticated PHP Object Injection ≤2.6.7Update to 2.6.8 | CVE-2026-97188 | |
| High8.8 | Unauthenticated PHP Object Injection ≤2.6.6Update to 2.6.7 | CVE-2024-10936 | |
| High8.8 | Cross-Site Request Forgery to PHAR Deserialization ≤2.5.0Update to 2.6.0 | CVE-2022-2434 |
- High8.1Unauthenticated PHP Object Injection
≤2.6.7Update to 2.6.8
- High8.8Unauthenticated PHP Object Injection
≤2.6.6Update to 2.6.7
- High8.8Cross-Site Request Forgery to PHAR Deserialization
≤2.5.0Update to 2.6.0
String locator: common questions
Does String locator have known vulnerabilities?
Yes. VulnCrest Radar lists 5 known vulnerabilities in String locator: 3 high, 2 medium. None are known to affect version null.
How do I check which version of String locator I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent String locator vulnerability?
CVE-2026-97188, published Oct 5, 2026: String Locator <= 2.6.7 - Unauthenticated PHP Object Injection. Severity: High (CVSS 8.1).
Is any String locator vulnerability listed in CISA KEV?
No. None of the known String locator vulnerabilities is currently listed in the CISA KEV catalog.