CVE-2022-2434: The String Locator plugin for WordPress is vulnerable to deserialization of untrusted input via the 'string-lo

Q: How do I fix CVE-2022-2434?

string locator: upgrade to newer than 2.5.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-2434 being exploited?

CVE-2022-2434 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-2434 affect?

CVE-2022-2434 affects string locator. Severity is high (CVSS 8.8). The String Locator plugin for WordPress is vulnerable to deserialization of untrusted input via the 'string-locator-path' parameter in versions up to, and including 2.5.0. This makes it possible for unauthenticated users to call files using

This month

HIGH 8.8UPGRADE

CVE-2022-2434 is a high-severity flaw (CVSS 8.8) affecting string locator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The String Locator plugin for WordPress is vulnerable to deserialization of untrusted input via the 'string-locator-path' parameter in versions up to, and including 2.5.0. This makes it possible for unauthenticated users to call files using a PHAR wrapper, granted they can trick a site administrator into performing an action such as clicking on a link, that will deserialize and call arbitrary PHP Objects that can be used to perform a variety of m

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.6% (top 25%)
CISA exploited list	No
Weakness	CWE-502
Published	2022-09-06
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: instawp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-09-06 18:15 UTCPublished CVE record published
2026-06-17 04:41 UTCUpdated Record last modified

instawp string locator UPGRADE

Affected: <= 2.5.0

Fixed in: newer than 2.5.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy string-locator || rpm -q string-locator || string-locator --version

2. UPGRADE to newer than 2.5.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade string-locator

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade string-locator

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-2434?

string locator: upgrade to newer than 2.5.0. Exact commands for each OS are on this page.

Is CVE-2022-2434 being exploited?

CVE-2022-2434 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-2434 affect?

CVE-2022-2434 affects string locator. Severity is high (CVSS 8.8). The String Locator plugin for WordPress is vulnerable to deserialization of untrusted input via the 'string-locator-path' parameter in versions up to, and including 2.5.0. This makes it possible for unauthenticated users to call files using

How urgent is CVE-2022-2434?

Priority 50/100. High severity

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

CVE-2024-10936 HIGH 8.8 UPGRADE The String locator plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and inclu
CVE-2023-6987 MEDIUM 6.1 UPGRADE The String locator plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'sql-column' p
CVE-2022-0493 MEDIUM 4.9 UPGRADE The String locator WordPress plugin before 2.5.0 does not properly validate the path of the files to be search

References

← Back to latest CVEs