# CVE-2022-45374: WordPress Yet Another Related Posts Plugin (YARPP) plugin <= 5.30.4 - Local File Inclusion

> Attackers can exploit a path traversal flaw in the YARPP WordPress plugin to include arbitrary local files, potentially leading to code execution or data disclosure.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-cjv7-w6rc-6cxq

## What is CVE-2022-45374?

CVE-2022-45374 is a high-severity path traversal vulnerability in YARPP, published on 17 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in YARPP allows PHP Local File Inclusion.This issue affects YARPP: from n/a through 5.30.4.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Yarpp Yet Another Related Posts Plugin.

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

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

## Is CVE-2022-45374 being exploited?

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

## Other vulnerabilities in 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-4471](https://insights.sbomify.com/CVE-2022-4471/): YARPP - Yet Another Related Posts Plugin < 5.30.3 - Contributor+ Stored XSS (medium 6.8)
- [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-45374 and fix it if it is affected.

What it is: CVE-2022-45374 is a high-severity path traversal vulnerability in YARPP, published on 17 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45374 exists.

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

## Sources

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

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