# CVE-2022-2311: Find and Replace All < 1.3 - Reflected Cross Site Scripting

> Attackers can inject malicious scripts via unsanitized parameters in the Find and Replace All plugin settings page, potentially compromising user sessions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Nov 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-vmxx-9r5c-688g

## What is CVE-2022-2311?

CVE-2022-2311 is a medium-severity cross-site scripting vulnerability in Unknown Find and Replace All, published on 28 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Find and Replace All WordPress plugin before 1.3 does not sanitize and escape some parameters from its setting page before outputting them back to the user, leading to a Reflected Cross-Site Scripting issue.

## Which versions are affected by CVE-2022-2311?

It affects 1 product.


Products: Find and Replace All Project Find and Replace All.

## How do I fix CVE-2022-2311?

No fix has been published for CVE-2022-2311 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-2311 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2311 exists.

## Other vulnerabilities in Unknown Find and Replace All

- [CVE-2022-3850](https://insights.sbomify.com/CVE-2022-3850/): Find and Replace All <= 1.3 - Arbitrary Replacement via CSRF (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2311 and fix it if it is affected.

What it is: CVE-2022-2311 is a medium-severity cross-site scripting vulnerability in Unknown Find and Replace All, published on 28 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-2311 exists.

Affected product: Unknown Find and Replace All. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2311/ (Markdown: https://insights.sbomify.com/CVE-2022-2311/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2311
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2311
- OSV: https://osv.dev/vulnerability/CVE-2022-2311

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2311/
Summaries are generated and may contain mistakes; the official description above is the record.