VulnerabilityPublished 28 Oct 2026

CVE-2026-61572: WWBN AVideo-Encoder · Server-Side Request Forgery (SSRF)

Affects WWBN AVideo-EncoderSource CVE Database V5

Not known to be exploited · CVSS 8.6 High : upgrade to 8.1.0 soon.

Data as of 28 Oct 2026, 22:12 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 8.1.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade AVideo-Encoder and wwbn/AVideo-Encoder to 8.1.0.

Affected software

Product	Affected	Fixed in
WWBNAVideo-Encoder	Affected <8.1.0	Fixed in 8.1.0
GitHubwwbn/AVideo-Encoder`pkg:github/wwbn/AVideo-Encoder`Other threats	Affected <8.1.0	Fixed in 8.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Version 8.1.0 contains an initial remediation that removes raw-response reflection and adds destination checks. However, private network exemptions and TLS verification defaults remain, so complete remediation is not yet achieved. Until full remediation is confirmed, restrict network access to the AVideo-Encoder server to trusted sources and internal services to reduce exposure.

Description

CVE-2026-61572 is a Server-Side Request Forgery (SSRF) vulnerability in WWBN AVideo-Encoder versions prior to 8.1.0. It allows unauthenticated remote attackers to make internal HTTP, HTTPS, and FTP requests, including access to cloud instance metadata and internal TCP services. The vulnerability arises from insufficient validation of URLs and acceptance of untrusted self-signed HTTPS certificates. Version 8.1.0 includes an initial remediation that removes raw-response reflection and adds destination checks but does not fully resolve all internal network and TLS verification issues.

Impact

An unauthenticated remote attacker can exploit this SSRF vulnerability to read internal HTTP and HTTPS responses, including sensitive cloud instance metadata credentials, and access internal TCP and FTP services. This can lead to information disclosure, partial integrity loss, and availability impact. The CVSS 3.1 score is 8.6 (High), reflecting the critical nature of the information exposure and potential service disruption.

Summary

The vulnerability in AVideo-Encoder (before 8.1.0) involves the function `url_get_contents` in `objects/functions.php` which accepts user-controlled URLs after only syntax validation, without blocking private, loopback, or link-local addresses, and disables TLS peer verification. The `Login::isLogged` function reauthenticates using attacker-controlled cookies, and the unauthenticated `objects/login.json.php` endpoint returns the fetched response, enabling full response exfiltration. The default operator allowlist is empty, allowing requests to any site. Additionally, an FTP variant in `view/youtubeDl.json.php` allows unauthenticated attackers to connect to internal FTP services. The initial fix in version 8.1.0 removes raw response reflection and adds some destination checks but leaves private network exemptions and TLS verification issues unresolved.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 21:58 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats