# CVE-2024-52484: WordPress Wc Recently viewed products plugin <= 1.0.1 - Reflected Cross Site Scripting (XSS) vulnerability

> Reflected XSS in the Wc Recently viewed products WordPress plugin allows attackers to execute arbitrary scripts in victim browsers.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 2 Dec 2024
- **Updated:** 11 May 2026
- **Also known as:** GHSA-fm4v-96pc-pw3x

## What is CVE-2024-52484?

CVE-2024-52484 is a high-severity cross-site scripting vulnerability in deepintowp Wc Recently viewed products, published on 2 Dec 2024. 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

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in deepintowp Wc Recently viewed products wc-recently-viewed-products allows Reflected XSS.This issue affects Wc Recently viewed products: from n/a through <= 1.0.1.

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

## Which versions are affected by CVE-2024-52484?


## How do I fix CVE-2024-52484?

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

## Is CVE-2024-52484 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52484 and fix it if it is affected.

What it is: CVE-2024-52484 is a high-severity cross-site scripting vulnerability in deepintowp Wc Recently viewed products, published on 2 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-52484 in the wild and no public exploit code.

Affected product: deepintowp Wc Recently viewed products. 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-2024-52484/ (Markdown: https://insights.sbomify.com/CVE-2024-52484/index.md)
```

## Sources

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

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