Deserialization in String Locator
CVE-2026-97188
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.
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- String Locator
Weakness classification (CWE)
References
- wpscan.com/vulnerability/cfb495ac-32fc-43e2-81b4-74faa8c164a4/ (technical-description, exploit, vdb-entry)
Frequently asked questions
- What is CVE-2026-97188?
- CVE-2026-97188 is a high-severity vulnerability in String Locator, classified under Deserialization of Untrusted Data. CVSS score: 8.8/10. Published 2026-10-07.
- How severe is CVE-2026-97188?
- High severity. CVSS v3 base score is 8.8 out of 10.