# CVE-2026-43879: AVideo has Blind SSRF in YPTWallet Donation Webhook via Missing isSSRFSafeURL() Check and CURLOPT_FOLLOWLOCATION Redirect Bypass

> Authenticated users can trigger blind SSRF via donation webhooks, allowing access to internal network resources and metadata services.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** 11 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-wp38-whx3-xffh

## What is CVE-2026-43879?

CVE-2026-43879 is a medium-severity server-side request forgery vulnerability in WWBN AVideo, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. In versions up to and including 29.0, an authenticated user can configure their own donation-notification webhook URL to point at internal/loopback/metadata hosts (e.g. http://127.0.0.1:8080/..., http://169.254.169.254/latest/..., RFC1918 addresses). When any other user (including a second account owned by the same attacker) donates even a trivial amount via plugin/CustomizeUser/donate.json.php, the AVideo server issues a curl POST to the attacker-supplied URL, resulting in a blind SSRF. The handler uses only isValidURL() (which is a format check) and does not call the codebase's own isSSRFSafeURL() helper. Additionally, CURLOPT_FOLLOWLOCATION is enabled with no per-hop revalidation, so even if the stored URL were validated, an HTTP 307 from an attacker-controlled host could redirect the POST to internal targets. Commit aaacd48f29f1ff71d1eb5fc81d37605f593cefa9 contains an updated fix.

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

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

2 open source packages ship an affected version, including wwbn/avideo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wwbn/avideo` | Packagist | All versions to 29.0 | None |
| `wwbn/avideo` | Packagist | All versions to 29.0 | None |

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

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

## Is CVE-2026-43879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-43879 is a medium-severity server-side request forgery vulnerability in WWBN AVideo, published on 11 May 2026. 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-2026-43879 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions up to 29.0; no fix listed
- wwbn/avideo (Packagist): affected all versions up to 29.0; no fix listed

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-43879/ (Markdown: https://insights.sbomify.com/CVE-2026-43879/index.md)
```

## Sources

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

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