CVE-2026-33024: AVideo-Encoder has Unauthenticated Blind Server-Side Request Forgery via Public Thumbnail Generator
AVideo is a video-sharing Platform. Versions prior to 8.0 contain a Server-Side Request Forgery vulnerability (CWE-918) in the public thumbnail endpoints getImage.php and getImageMP4.php. Both endpoints accept a base64Url GET parameter, base64-decode it, and pass the resulting URL to ffmpeg as an input source without any authentication requirement. The prior validation only checked that the URL was syntactically valid (FILTERVALIDATEURL) and started with http(s)://. This is insufficient: an attacker can supply URLs such as http://169.254.169.254/latest/meta-data/ (AWS/cloud instance metadata), http://192.168.x.x/, or http://127.0.0.1/ to make the server reach internal network resources. The response is not directly returned (blind), but timing differences and error logs can be used to infer results. The issue has been fixed in version 8.0.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33024?
CVE-2026-33024 is classified as a medium severity vulnerability due to its potential for unauthenticated server-side request forgery.
How do I fix CVE-2026-33024?
To mitigate CVE-2026-33024, upgrade to AVideo or AVideo-Encoder version 8.0 or later.
What components are affected by CVE-2026-33024?
CVE-2026-33024 affects the AVideo and AVideo-Encoder software versions prior to 8.0.
Can CVE-2026-33024 be exploited remotely?
Yes, CVE-2026-33024 can be exploited remotely due to its unauthenticated nature.
What type of vulnerability is CVE-2026-33024?
CVE-2026-33024 is categorized as a Server-Side Request Forgery (SSRF) vulnerability.