CVE-2026-43884: CWE-918: Server-Side Request Forgery (SSRF) in WWBN AVideo
WWBN AVideo versions up to and including 29.0 contain a Server-Side Request Forgery (SSRF) vulnerability in two endpoints that validate user-supplied URLs but do not properly handle HTTP redirects. An attacker can exploit this by providing a URL that redirects to internal or cloud metadata addresses, bypassing SSRF protections. This vulnerability has a high severity score of 7.7 and affects confidentiality but not integrity or availability.
AI Analysis
Technical Summary
The vulnerability in WWBN AVideo (<= 29.0) involves two endpoints (plugin/AI/receiveAsync.json.php and objects/EpgParser.php) that use isSSRFSafeURL() to validate URLs before fetching them with PHP's file_get_contents(). However, file_get_contents() follows HTTP redirects automatically, and the validation only applies to the initial URL. An attacker can supply a URL that redirects (e.g., via HTTP 302) to internal or cloud metadata service addresses such as http://169.254.169.254/latest/meta-data/, effectively bypassing SSRF protections and potentially exposing sensitive internal information. A code commit (603e7bf77a835584387327e35560262feb075db3) contains an updated fix, but no official patch or vendor advisory is provided in the data.
Potential Impact
Successful exploitation allows an attacker with low privileges to cause the server to make HTTP requests to internal or cloud metadata endpoints, potentially exposing sensitive information such as cloud instance metadata. The CVSS score of 7.7 reflects a high impact on confidentiality. There is no indication of impact on integrity or availability. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The referenced commit suggests a fix is available in the source code repository. Until an official patch is released, users should avoid exposing the vulnerable endpoints or restrict access to trusted users only. Monitor the vendor's official channels for updates and apply the fix once it is officially released.
CVE-2026-43884: CWE-918: Server-Side Request Forgery (SSRF) in WWBN AVideo
Description
WWBN AVideo versions up to and including 29.0 contain a Server-Side Request Forgery (SSRF) vulnerability in two endpoints that validate user-supplied URLs but do not properly handle HTTP redirects. An attacker can exploit this by providing a URL that redirects to internal or cloud metadata addresses, bypassing SSRF protections. This vulnerability has a high severity score of 7.7 and affects confidentiality but not integrity or availability.
CVSS v3.1
Score 7.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in WWBN AVideo (<= 29.0) involves two endpoints (plugin/AI/receiveAsync.json.php and objects/EpgParser.php) that use isSSRFSafeURL() to validate URLs before fetching them with PHP's file_get_contents(). However, file_get_contents() follows HTTP redirects automatically, and the validation only applies to the initial URL. An attacker can supply a URL that redirects (e.g., via HTTP 302) to internal or cloud metadata service addresses such as http://169.254.169.254/latest/meta-data/, effectively bypassing SSRF protections and potentially exposing sensitive internal information. A code commit (603e7bf77a835584387327e35560262feb075db3) contains an updated fix, but no official patch or vendor advisory is provided in the data.
Potential Impact
Successful exploitation allows an attacker with low privileges to cause the server to make HTTP requests to internal or cloud metadata endpoints, potentially exposing sensitive information such as cloud instance metadata. The CVSS score of 7.7 reflects a high impact on confidentiality. There is no indication of impact on integrity or availability. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The referenced commit suggests a fix is available in the source code repository. Until an official patch is released, users should avoid exposing the vulnerable endpoints or restrict access to trusted users only. Monitor the vendor's official channels for updates and apply the fix once it is officially released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-04T15:17:09.329Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a028749cbff5d86108b51b3
Added to database: 05/12/2026, 01:50:01 UTC
Last enriched: 05/19/2026, 11:01:02 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.