CVE-2026-39370 | WWBN AVideo up to 26.0 aVideoEncoder.json.php downloadURL server-side request forgery (GHSA-cmcr-q4jf-p6q9)

VDB-355953 · CVE-2026-39370 · GHSA-CMCR-Q4JF-P6Q9 WWBN AVIDEO UP TO 26.0 AVIDEOENCODER.JSON.PHP DOWNLOADURL SERVER-SIDE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.6 $0-$5k 1.50 Summaryinfo A vulnerability has been found in WWBN AVideo up to 26.0 and classified as critical. This issue affects some unknown processing of the file objects/aVideoEncoder.json.php. Performing a manipulation of the argument downloadURL results in server-side request forgery. This vulnerability was named CVE-2026-39370. The attack may be initiated remotely. There is no available exploit. Detailsinfo A vulnerability, which was classified as critical, was found in WWBN AVideo up to 26.0. This affects an unknown part of the file objects/aVideoEncoder.json.php. The manipulation of the argument downloadURL with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is: WWBN AVideo is an open source video platform. In versions 26.0 and prior, objects/aVideoEncoder.json.php still allows attacker-controlled downloadURL values with common media or archive extensions such as .mp4, .mp3, .zip, .jpg, .png, .gif, and .webm to bypass SSRF validation. The server then fetches the response and stores it as media content. This allows an authenticated uploader to turn the upload-by-URL flow into a reliable SSRF response-exfiltration primitive. The vulnerability is caused by an incomplete fix for CVE-2026-27732. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-39370 since 04/06/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/07/2026). By approaching the search of inurl:objects/aVideoEncoder.json.php it is possible to find vulnerable targets with Google Hacking. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Vendor WWBN Name AVideo Version 26.0 License open-source Website Product: https://github.com/WWBN/AVideo/ CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.7 VulDB Meta Temp Score: 6.6 VulDB Base Score: 6.3 VulDB Temp Score: 6.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.1 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Server-side request forgery CWE: CWE-918 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Google Hack: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/06/2026 CVE reserved 04/07/2026 +1 days Advisory disclosed 04/07/2026 +0 days VulDB entry created 04/07/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-cmcr-q4jf-p6q9 Status: Not defined CVE: CVE-2026-39370 (🔒) GCVE (CVE): GCVE-0-2026-39370 GCVE (VulDB): GCVE-100-355953 Entryinfo Created: 04/07/2026 23:34 Changes: 04/07/2026 23:34 (64) Complete: 🔍 Cache ID: 99:26B:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸