# CVE-2022-4471: YARPP - Yet Another Related Posts Plugin < 5.30.3 - Contributor+ Stored XSS

> Contributors can inject malicious scripts via shortcode attributes in the YARPP plugin, leading to stored XSS attacks.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 13 Feb 2023
- **Updated:** 21 Mar 2025
- **Also known as:** GHSA-fwq8-9vrm-w64h

## What is CVE-2022-4471?

CVE-2022-4471 is a medium-severity cross-site scripting vulnerability in Unknown YARPP, published on 13 Feb 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The YARPP WordPress plugin before 5.30.3 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks

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

It affects 1 product.


Products: Yarpp Yet Another Related Posts Plugin.

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

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

## Is CVE-2022-4471 being exploited?

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

## Other vulnerabilities in Unknown YARPP

- [CVE-2023-0579](https://insights.sbomify.com/CVE-2023-0579/): YARPP - Yet Another Related Posts Plugin < 5.30.3 - Subscriber+ SQLi (high 8.8)
- [CVE-2022-45374](https://insights.sbomify.com/CVE-2022-45374/): WordPress Yet Another Related Posts Plugin (YARPP) plugin <= 5.30.4 - Local File Inclusion (high 7.7)
- [CVE-2023-2433](https://insights.sbomify.com/CVE-2023-2433/): YARPP – Yet Another Related Posts Plugin <= 5.30.3 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2024-43919](https://insights.sbomify.com/CVE-2024-43919/): WordPress Yet Another Related Posts Plugin (YARPP) plugin <= 5.30.10 - Broken Access Control vulnerability (medium 5.3)
- [CVE-2023-6495](https://insights.sbomify.com/CVE-2023-6495/): YARPP – Yet Another Related Posts Plugin <= 5.30.9 - Authenticated(Administrator+) Cross-Site Scripting (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4471 is a medium-severity cross-site scripting vulnerability in Unknown YARPP, published on 13 Feb 2023. An attacker needs administrator access to exploit it, 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-4471 exists.

Affected product: Unknown YARPP. 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-4471/ (Markdown: https://insights.sbomify.com/CVE-2022-4471/index.md)
```

## Sources

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

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