AVideo has an Unauthenticated Video Password Brute-Force Vulnerability via Unrate-Limited Boolean Oracle

published 2026-03-26 7 mo ago modified 2026-10-26 13 d ago also GHSA-8prq-2jr2-cm92 , EUVD-2026-16648

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits: 0; none known

WWBN AVideo is an open source video platform. In versions up to and including 26.0, the `get_api_video_password_is_correct` API endpoint allows any unauthenticated user to verify whether a given password is correct for any password-protected video. The endpoint returns a boolean `passwordIsCorrect` field with no rate limiting, CAPTCHA, or authentication requirement, enabling efficient offline-speed brute-force attacks against video passwords. Commit 01a0614fedcdaee47832c0d913a0fb86d8c28135 contains a patch.

Patch / fix

links 1

github.com/WWBN/AVideo@01a0614 commit

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 7 mo ago (2026-03-30)

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/WWBN/AVideo/security/advisories/GHSA-8prq-2jr2-cm92 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	wwbn/avideo	<=26.0	no fix listed

Affected products

WWBN AVideo

Classification

Weakness

CWE-307 Improper Restriction of Excessive Authentication Attempts

References

github.com /WWBN/AVideo/commit/01a0614fedcdaee47832c0d913a0fb86d8c28135
web, patch
github.com /WWBN/AVideo/security/advisories/GHSA-8prq-2jr2-cm92
web, exploit, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2026-33763
advisory
github.com /WWBN/AVideo
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary