# CVE-2026-33767: AVideo has SQL Injection via Partial Prepared Statement — videos_id Concatenated Directly into Query

> Attackers can inject arbitrary SQL via the videos_id parameter in AVideo's like.php, potentially reading or modifying database contents.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-fj74-qxj7-r3vc

## What is CVE-2026-33767?

CVE-2026-33767 is a high-severity SQL injection vulnerability in Wwbn Avideo, published on 27 Mar 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 26.0, in `objects/like.php`, the `getLike()` method constructs a SQL query using a prepared statement placeholder (`?`) for `users_id` but directly concatenates `$this->videos_id` into the query string without parameterization. An attacker who can control the `videos_id` value (via a crafted request) can inject arbitrary SQL, bypassing the partial prepared-statement protection. Commit 0215d3c4f1ee748b8880254967b51784b8ac4080 contains a patch.

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

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

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 | 26.0 |
| `wwbn/avideo` | Packagist | All versions | 26.0 |

Products: Wwbn Avideo.

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

Upgrade wwbn/avideo to 26.0 or later.

## Is CVE-2026-33767 being exploited?

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

## 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-33767 and fix it if it is affected.

What it is: CVE-2026-33767 is a high-severity SQL injection vulnerability in Wwbn Avideo, published on 27 Mar 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-33767 exists.

Affected packages and fixed versions:
- wwbn/avideo (Packagist): affected all versions; fixed in 26.0
- wwbn/avideo (Packagist): affected all versions; fixed in 26.0

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

## Sources

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

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