WordPress security changelog
HIGH CVE-2022-2434 Modified

String Locator: Code execution

String Locator is affected by code execution. The vulnerable path is reachable without authentication. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

CVE / CNA score 8.8 CVSS 3.1 · security@wordfence.com
NVD score 8.8 CVSS 3.1 · nvd@nist.gov
Component
String Locator
Plugin slug
string-locator
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Sep 06, 2022
Weakness
CWE-502 — Deserialization of Untrusted Data

This CVE was published Sep 06, 2022 and is one of 4 known issues for this plugin.

Update, patch or deactivate.

Update String Locator to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

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 malicious actions granted a POP chain is also present. It also requires that the attacker is successful in uploading a file with the serialized payload.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary and upstream sources