LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2434: String Locator <= 2.5.0 - Cross-Site Request Forgery to PHAR Deserialization

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.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-2434 affects the WordPress String Locator plugin up to version 2.5.0. An attacker could abuse an administrator’s browser action to trigger unsafe PHP object deserialization. Successful exploitation has serious confidentiality, integrity, and availability impact, but requires user interaction and other conditions.

Executive priority

Treat as a high-priority WordPress plugin exposure, especially for internet-facing sites with active administrators. Prioritize inventory and update confirmation before broader incident response, because the supplied sources do not show active exploitation.

Technical view

The issue is CWE-502 deserialization of untrusted input through the string-locator-path parameter. Sources describe CSRF-driven use of a PHAR wrapper, requiring an administrator action, an attacker-uploaded serialized payload file, and a usable POP chain. CVSS 3.1 is 8.8 high.

Likely exposure

Exposure is most likely on WordPress sites running String Locator version 2.5.0 or earlier. Confirm plugin inventory directly because the source bundle includes inconsistent affected-product metadata while the description clearly names versions through 2.5.0.

Exploitation context

The bundle does not support a claim of active exploitation, and KEV status is false. Exploitation is not purely drive-by: it requires administrator interaction plus prior placement of a serialized payload file and compatible PHP object gadget conditions.

Researcher notes

Focus validation on the string-locator-path handling, PHAR-wrapper reachability, CSRF protection, and whether a site has a relevant POP chain. Do not assume exploitability without upload placement and gadget-chain conditions. Fixed-version evidence is incomplete in the supplied bundle.

Mitigation direction

  • Identify all WordPress sites using the String Locator plugin.
  • Upgrade String Locator beyond version 2.5.0 if vendor guidance confirms remediation.
  • If upgrade status is unclear, check WordPress plugin and vendor advisory guidance.
  • Restrict administrator sessions and reduce unnecessary plugin access.
  • Review file upload controls and remove untrusted uploaded files where appropriate.

Validation and detection

  • Check installed String Locator versions across managed WordPress sites.
  • Confirm whether any site runs version 2.5.0 or earlier.
  • Review plugin changelog or WordPress Trac changeset for remediation details.
  • Verify administrator-only workflows include CSRF protections after updating.
  • Look for suspicious uploaded files tied to affected sites.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-2434 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-2434Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
instawpString locator0unaffected
Weakness

CWE details

CWE-502

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs