dbcve.org
AvideoApplication · Wwbn

CVE-2026-39370

HIGH · 7.1 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to after 26.0 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WWBN AVideo versions 26.0 and prior contain an SSRF bypass vulnerability in objects/aVideoEncoder.json.php. Attackers can use common media or archive file extensions (.mp4, .mp3, .zip, .jpg, .png, .gif, .webm) in downloadURL parameters to bypass incomplete SSRF validation from a prior fix (CVE-2026-27732). This allows authenticated uploaders to abuse the upload-by-URL feature as a reliable SSRF response-exfiltration primitive, causing the server to fetch and store arbitrary content.

MitigationImplement comprehensive SSRF protection using URL allowlists and strict scheme validation (only http/https), not relying on file extension filtering. Validate the full URL resolution path to prevent internal resource access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AvideoApplication
Affected:<= 26.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Avideo installation and version
    Locate the Avideo installation directory and check the version file (typically version.txt or in the database configuration). Compare the installed version against the affected range <= 26.0.
    Affected if The installed version is 26.0 or lower.
  2. Verify upload-by-URL endpoint exists
    Check for the presence of the file objects/aVideoEncoder.json.php in the web root directory.
    Affected if The file objects/aVideoEncoder.json.php exists on the server.
  3. Confirm downloadURL parameter acceptance
    Examine the source code of objects/aVideoEncoder.json.php to verify it accepts a downloadURL parameter. Look for code that processes this parameter for fetching external content.
    Affected if The endpoint accepts and processes a downloadURL parameter.
  4. Check for extension validation bypass
    Review the code in objects/aVideoEncoder.json.php to see if it validates file extensions in the downloadURL. Specifically look for whether extensions like .mp4, .mp3, .zip, .jpg, .png, .gif, .webm are accepted without proper URL allowlisting.
    Affected if The code accepts common media/archive extensions (.mp4, .mp3, .zip, .jpg, .png, .gif, .webm) in the URL without strict validation.

The server is affected if it is running Wwbn Avideo version 26.0 or lower and the objects/aVideoEncoder.json.php file exists with the downloadURL parameter accepting unrestricted file extensions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 26.0
Interim mitigation

Implement comprehensive SSRF protection using URL allowlists and strict scheme validation (only http/https), not relying on file extension filtering. Validate the full URL resolution path to prevent internal resource access.

Fix this in Avideo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39370 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data