← Back to results
Vulnerability record · public intelligence
CVE-2026-41055
HIGH

WWBN AVideo has an incomplete fix for CVE-2026-33039: SSRF

Published Apr 21, 2026 · Updated Nov 3, 2026

Severity · CVSSHIGH · Not scored
Known exploitationNot listed
EPSS / likelihood0.38%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

WWBN AVideo has an incomplete fix for CVE-2026-33039: SSRF

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

The incomplete SSRF fix in AVideo's LiveLinks proxy adds isSSRFSafeURL() validation but leaves DNS TOCTOU vulnerabilities where DNS rebinding between validation and the actual HTTP request redirects traffic to internal endpoints.

Potential impact

DNS rebinding allows an attacker to bypass SSRF validation and make the server send requests to internal services, cloud metadata endpoints, and other protected resources.

Technical context

The plugin/LiveLinks/proxy.php endpoint proxies live stream URLs. The fix adds isSSRFSafeURL() check on the initial URL, redirect URL validation, and followlocation=0 in the getheaders() context. However, multiple DNS TOCTOU vulnerabilities remain. For the initial URL, isSSRFSafeURL() resolves DNS once for validation, but getheaders() resolves DNS again independently. A DNS rebinding attack with TTL=0 returns a safe external IP for the first resolution and an internal IP for the second. The same TOCTOU exists for redirect URLs: isSSRFSafeURL() validates the redirect target (first resolution returns a safe IP), then fakeBrowser() makes the actual request (second resolution returns an internal IP). Additionally, even with followlocation=0, getheaders() still sends an HTTP request that can probe internal services via DNS rebinding, and multiple Location headers in a response cause filtervar() to receive an array instead of a string, resulting in a fall-through to the else branch.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5NVD-MODIFIED
SSVC priority
MEDIUM
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Patch commit ↗
  2. Patch commit ↗
  3. Security advisory ↗
  4. Security advisory ↗

Record history

Published Apr 21, 2026 · Last refreshed Nov 3, 2026