CVE-2026-33512: AVideo has an unauthenticated decrypt oracle leaking any ciphertext

Published Mar 20, 2026
·
Updated

Summary The API plugin exposes a decryptString action without any authentication. Anyone can submit ciphertext and receive plaintext. Ciphertext is issued publicly (e.g., view/url2Embed.json.php), so any user can recover protected tokens/metadata. Severity: High.

Details - Entry: plugin/API/get.json.php is unauthenticated. - Handler: plugin/API/API.php getapidecryptString() (lines ~5945–5966): php $string = decryptString($REQUEST['string']); return new ApiObject($string, empty($string)); No APISecret or user check occurs before decrypting. - Public ciphertext source: view/url2Embed.json.php returns playLink/playEmbedLink (encryptString(jsonencode(...))) to any caller.

PoC 1. Obtain ciphertext: GET /view/url2Embed.json.php?url=https://example.com/video.mp4 Copy playLink. 2. Decrypt without auth: POST /plugin/API/get.json.php?APIName=decryptString Content-Type: application/x-www-form-urlencoded

string=<playLink ciphertext> Response contains the plaintext JSON (videoLink, title, usersid, etc.).

Impact - Any encrypted payload produced by the platform can be decrypted by anyone. - Leaks tokens/links intended to be confidential; enables replay and tampering where secrecy was assumed.

Mitigation - Require API secret or authenticated/authorized user for decryptString, or remove the endpoint. - Prefer one-way signatures (HMAC) instead of exposing generic decryption. - Rotate encryption keys/salts after patch to invalidate exposed ciphertexts.

Other sources

WWBN AVideo is an open source video platform. In versions up to and including 26.0, the API plugin exposes a decryptString action without any authentication. Anyone can submit ciphertext and receive plaintext. Ciphertext is issued publicly (e.g., view/url2Embed.json.php), so any user can recover protected tokens/metadata. Commit 3fdeecef37bb88967a02ccc9b9acc8da95de1c13 contains a patch.

MITRE

Affected Software

3 affected components
WWBN AVideo<=26.0
composer/wwbn/avideo<=26.0
WWBN AVideo<=26.0

Event History

Mar 20, 2026
Advisory Published
via GitHub·09:55 PM
Data Sourced
via GitHub·09:55 PM
DescriptionSeverityWeaknessAffected Software
Mar 23, 2026
CVE Published
via MITRE·06:17 PM
Data Sourced
via MITRE·06:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-33512?

CVE-2026-33512 is considered a critical vulnerability due to its potential for unauthorized access to plaintext data.

2

How do I fix CVE-2026-33512?

To fix CVE-2026-33512, upgrade to AVideo version 26.1 or later, where the unauthenticated decrypt oracle has been addressed.

3

What versions of AVideo are affected by CVE-2026-33512?

AVideo versions up to and including 26.0 are affected by CVE-2026-33512.

4

What type of vulnerability is CVE-2026-33512?

CVE-2026-33512 is an unauthenticated decrypt oracle vulnerability allowing exposure of sensitive information.

5

Can CVE-2026-33512 be exploited remotely?

Yes, CVE-2026-33512 can be exploited remotely as it does not require authentication to access the vulnerable API.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203