How severe is CVE-2026-39370?

CVE-2026-39370 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability none.

Is CVE-2026-39370 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-39370?

CVE-2026-39370 affects Wwbn Avideo. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-39370?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-39370 have an EU (EUVD) identifier?

Yes. CVE-2026-39370 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-19886.

When was CVE-2026-39370 published?

CVE-2026-39370 was published on 2026-04-07 and last updated on 2026-06-17.

CVE-2026-39370

CVE-2026-39370 is a high-severity vulnerability in Wwbn Avideo with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-918.

Key facts

Severity: High (CVSS 3.x base score 7.1)
EPSS exploit prediction: 0% (11th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-19886
Weakness: CWE-918
Affected product: Wwbn Avideo
Published: 2026-04-07
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-39370?: 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.
How severe is CVE-2026-39370?: CVE-2026-39370 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability none.
Is CVE-2026-39370 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-39370?: CVE-2026-39370 affects Wwbn Avideo. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-39370?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-39370 have an EU (EUVD) identifier?: Yes. CVE-2026-39370 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-19886.
When was CVE-2026-39370 published?: CVE-2026-39370 was published on 2026-04-07 and last updated on 2026-06-17.

References

https://github.com/WWBN/AVideo/security/advisories/GHSA-cmcr-q4jf-p6q9

Affected products (1)

cpe:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*

More vulnerabilities in Wwbn Avideo

CVE-2026-40911 — Critical (CVSS 10.0): WWBN AVideo is an open source video platform. In versions 29.0 and prior, the YPTSocket plugin's WebSocket server…
CVE-2026-33478 — Critical (CVSS 10.0): WWBN AVideo is an open source video platform. In versions up to and including 26.0, multiple vulnerabilities in…
CVE-2022-30547 — Critical (CVSS 9.9): A directory traversal vulnerability exists in the unzipDirectory functionality of WWBN AVideo 11.6 and dev master…
CVE-2026-41304 — Critical (CVSS 9.8): WWBN AVideo is an open source video platform. In versions 29.0 and below, the `cloneServer.json.php` endpoint in the…
CVE-2026-33770 — Critical (CVSS 9.8): WWBN AVideo is an open source video platform. In versions up to and including 26.0, the `fixCleanTitle()` static method…
CVE-2026-33352 — Critical (CVSS 9.8): WWBN AVideo is an open source video platform. Prior to version 26.0, an unauthenticated SQL injection vulnerability…

All CVEs affecting Wwbn Avideo →

Other CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities

CVE-2026-47938 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) versions 7.4.3 build 9394 and earlier are affected by a Server-Side Request Forgery (SSRF)…
CVE-2026-35431 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Microsoft Entra ID Entitlement Management allows an unauthorized attacker to…
CVE-2026-32186 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Microsoft Bing allows an unauthorized attacker to elevate privileges over a…
CVE-2026-33107 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Azure Databricks allows an unauthorized attacker to elevate privileges over a…
CVE-2026-32871 — Critical (CVSS 10.0): FastMCP is a Pythonic way to build MCP servers and clients. Prior to version 3.2.0, the OpenAPIProvider in FastMCP…
CVE-2026-32169 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Azure Cloud Shell allows an unauthorized attacker to elevate privileges over a…

Browse all CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities →