# CVE-2022-47587: WordPress WP Search Analytics Plugin <= 1.4.5 is vulnerable to Cross Site Scripting (XSS)

> Authenticated administrators can inject malicious scripts into the WP Search Analytics plugin, potentially leading to code execution or account takeover.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 May 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-fvc7-4rqw-m8qw

## What is CVE-2022-47587?

CVE-2022-47587 is a medium-severity cross-site scripting vulnerability in Cornel Raiu WP Search Analytics, published on 10 May 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Cornel Raiu WP Search Analytics plugin <= 1.4.5 versions.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Wp Search Analytics Project Wp Search Analytics.

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

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

## Is CVE-2022-47587 being exploited?

There is no known exploitation of CVE-2022-47587 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47587 is a medium-severity cross-site scripting vulnerability in Cornel Raiu WP Search Analytics, published on 10 May 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-47587 in the wild and no public exploit code.

Affected product: Cornel Raiu WP Search Analytics. 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-47587/ (Markdown: https://insights.sbomify.com/CVE-2022-47587/index.md)
```

## Sources

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

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