# CVE-2024-13879: Stream <= 4.0.2 - Authenticated (Admin+) Server-Side Request Forgery

> Administrators can exploit insufficient webhook validation to perform server-side requests, accessing or modifying internal service data.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/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:** 17 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-fjjc-v9rc-xhj8

## What is CVE-2024-13879?

CVE-2024-13879 is a medium-severity server-side request forgery vulnerability in xwp Stream, published on 17 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Stream plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.0.2 due to insufficient validation on the webhook feature. This makes it possible for authenticated attackers, with administrator-level access and above, to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.

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

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


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

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

## Is CVE-2024-13879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13879 is a medium-severity server-side request forgery vulnerability in xwp Stream, published on 17 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13879 in the wild and no public exploit code.

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

## Sources

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

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