# CVE-2026-89000: WPeMatico RSS Feed Fetcher < 2.8.27 - Contributor+ SSRF via Campaign Run

> Contributors can exploit missing validation in WPeMatico RSS Feed Fetcher to perform Server-Side Request Forgery and access internal resources.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-x8xr-q2j9-gfc2

## What is CVE-2026-89000?

CVE-2026-89000 is a medium-severity server-side request forgery vulnerability in Unknown WPeMatico RSS Feed Fetcher, published on 27 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The WPeMatico RSS Feed Fetcher WordPress plugin before 2.8.27 does not perform a capability check or validate the destination of a user-supplied feed URL before fetching it server-side, allowing users with contributor-level access and above to make the server issue requests to internal-only resources and read the responses back.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-89000 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89000 is a medium-severity server-side request forgery vulnerability in Unknown WPeMatico RSS Feed Fetcher, published on 27 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89000 in the wild and no public exploit code.

Affected product: Unknown WPeMatico RSS Feed Fetcher. 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-89000/ (Markdown: https://insights.sbomify.com/CVE-2026-89000/index.md)
```

## Sources

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

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