# CVE-2026-109980: The Related Posts for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-jcpv-fxpw-qc4w

## What is CVE-2026-109980?

CVE-2026-109980 is a medium-severity vulnerability in barrykooij Related Posts for WordPress, published on 28 Oct 2026. 

### Official description

The Related Posts for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.0 via the 'rp4wp_view' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to extract the titles and publication dates of all private posts site-wide, normally restricted to Editor-level users and above. The page's existing authorization check only verifies edit_posts and edit_post on a parent post the attacker owns, both of which any Contributor satisfies, leaving no effective gate against reading other authors' private posts.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-109980?


## How do I fix CVE-2026-109980?

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

## Is CVE-2026-109980 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109980 and fix it if it is affected.

What it is: CVE-2026-109980 is a medium-severity vulnerability in barrykooij Related Posts for WordPress, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-109980 in the wild and no public exploit code.

Affected product: barrykooij Related Posts for WordPress. 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-2026-109980/ (Markdown: https://insights.sbomify.com/CVE-2026-109980/index.md)
```

## Sources

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

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