VulnerabilityPublished 21 Apr 2026

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

Affects WWBN AVideoSource CVE Database V5

Not known to be exploited · CVSS 7.7 High.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

7.7High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Apr 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 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

Affected software

Product	Affected	Fixed in
WWBNAVideo	Affected <=29.0	Fixed in–
GitHubwwbn/AVideo`pkg:github/wwbn/AVideo`Other threats	Affected <=29.0	Fixed in–

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

AI-suggested

A patch fixing this vulnerability is available in commit a0156a6398362086390d949190f9d52a823000ba. Users of WWBN AVideo versions 29.0 and below should upgrade to a version that includes this fix. Since no official vendor advisory or patch link is provided, verify the fix by applying the referenced commit or checking the vendor's repository for updated releases. Until patched, avoid exposing the affected service to untrusted users or networks to reduce risk.

Description

CVE-2026-41060 is a Server-Side Request Forgery (SSRF) vulnerability in WWBN AVideo versions 29.0 and below. The vulnerability arises from the isSSRFSafeURL() function, which incorrectly allows URLs with the same hostname as the site to bypass SSRF protections regardless of port. This enables attackers to access arbitrary ports on the AVideo server. The response from such requests is saved to a web-accessible location, allowing attackers to exfiltrate data. A fix for this issue is available in commit a0156a6398362086390d949190f9d52a823000ba.

Impact

An attacker with at least low privileges can exploit this SSRF vulnerability to make the server send requests to arbitrary ports on itself, bypassing intended SSRF protections. This can lead to unauthorized access to internal services running on non-standard ports. The exfiltration of response data is possible because the server saves responses to a web-accessible location. The vulnerability does not impact integrity or availability but has high confidentiality impact due to potential data exposure.

Summary

WWBN AVideo versions 29.0 and earlier contain an SSRF vulnerability due to improper validation in the isSSRFSafeURL() function located in objects/functions.php. The function short-circuits SSRF protections for any URL whose hostname matches the webSiteRootURL, ignoring the port number. This allows attackers to send requests to arbitrary ports on the same server, potentially accessing internal services. The server saves the response body to a web-accessible path, enabling attackers to retrieve the response data externally. The vulnerability is tracked as CWE-918 and has a CVSS 3.1 base score of 7.7 (high severity). The issue is fixed in a specific commit referenced in the description.

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 29 Apr 2026, 11:38 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats