# CVE-2026-43884: WWBN AVideo: SSRF Protection Bypass via HTTP Redirect and DNS Rebinding in isSSRFSafeURL()

> Attackers can bypass SSRF protections in AVideo via HTTP redirects to access internal resources or cloud metadata.

- **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:** 11 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-2hch-c97c-g99x

## What is CVE-2026-43884?

CVE-2026-43884 is a high-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, two endpoints (plugin/AI/receiveAsync.json.php and objects/EpgParser.php) in AVideo call isSSRFSafeURL() to validate user-supplied URLs, then fetch them using bare file_get_contents() without disabling PHP's automatic redirect following. An attacker can supply a URL pointing to a server they control that returns a 302 redirect to an internal/cloud-metadata address (e.g., http://169.254.169.254/latest/meta-data/). Since isSSRFSafeURL() only validates the initial URL, the redirect target bypasses all SSRF protections. Commit 603e7bf77a835584387327e35560262feb075db3 contains an updated fix.

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

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

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-43884?

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

## Is CVE-2026-43884 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-43884 is a high-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: There is no known exploitation of CVE-2026-43884 in the wild and no public exploit code.

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

## Sources

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

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