# CVE-2026-28501: WWBN AVideo: Unauthenticated SQL Injection via JSON Request Bypass in objects/videos.json.php

> Unauthenticated attackers can execute SQL commands via unsanitized JSON input in AVideo, allowing unauthorized data access or modification.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-pv87-r9qf-x56p

## What is CVE-2026-28501?

CVE-2026-28501 is a critical SQL injection vulnerability in Wwbn Avideo, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WWBN AVideo is an open source video platform. Prior to version 24.0, an unauthenticated SQL Injection vulnerability exists in AVideo within the objects/videos.json.php and objects/video.php components. The application fails to properly sanitize the catName parameter when it is supplied via a JSON-formatted POST request body. Because JSON input is parsed and merged into $_REQUEST after global security checks are executed, the payload bypasses the existing sanitization mechanisms. This issue has been patched in version 24.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

2 open source packages ship an affected version, including wwbn/avideo. It affects 1 product.


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

Products: Wwbn Avideo.

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

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

## Is CVE-2026-28501 being exploited?

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

Public exploit code:

- AVideo Unauthenticated SQL Injection Credential Dump (metasploit)

## Other vulnerabilities in Wwbn Avideo

- [CVE-2026-40911](https://insights.sbomify.com/CVE-2026-40911/): WWBN AVideo YPTSocket WebSocket Broadcast Relay Leads to Unauthenticated Cross-User JavaScript Execution via Client-Side eval() Sinks (critical 10.0)
- [CVE-2026-33478](https://insights.sbomify.com/CVE-2026-33478/): AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection (critical 10.0)
- [CVE-2022-30534](https://insights.sbomify.com/CVE-2022-30534/): Command injection in AVideo (critical 9.9)
- [CVE-2022-30547](https://insights.sbomify.com/CVE-2022-30547/): Path traversal in AVideo (critical 9.9)
- [CVE-2022-32572](https://insights.sbomify.com/CVE-2022-32572/): Command injection in AVideo (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28501 is a critical SQL injection vulnerability in Wwbn Avideo, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28501 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions up to 21.0.0; no fix listed
- wwbn/avideo (Packagist): affected all versions up to 21.0.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-28501/ (Markdown: https://insights.sbomify.com/CVE-2026-28501/index.md)
```

## Sources

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

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