CVE-2026-27732: CWE-918: Server-Side Request Forgery (SSRF) in WWBN AVideo
WWBN AVideo is an open source video platform. Prior to version 22.0, the `aVideoEncoder.json.php` API endpoint accepts a `downloadURL` parameter and fetches the referenced resource server-side without proper validation or an allow-list. This allows authenticated users to trigger server-side requests to arbitrary URLs (including internal network endpoints). An authenticated attacker can leverage SSRF to interact with internal services and retrieve sensitive data (e.g., internal APIs, metadata services), potentially leading to further compromise depending on the deployment environment. This issue has been fixed in AVideo version 22.0.
AI Analysis
Technical Summary
CVE-2026-27732 is a Server-Side Request Forgery (SSRF) vulnerability identified in WWBN's open-source video platform, AVideo, specifically in versions prior to 22.0. The vulnerability resides in the aVideoEncoder.json.php API endpoint, which accepts a parameter named downloadURL. This parameter is used by the server to fetch external resources without adequate validation or an allow-list mechanism. As a result, an authenticated attacker can manipulate this parameter to force the server to initiate HTTP requests to arbitrary URLs, including internal network addresses that are typically inaccessible externally. This SSRF flaw can be leveraged to interact with internal services such as metadata services, internal APIs, or other sensitive endpoints, potentially exposing confidential information or enabling lateral movement within the network. The vulnerability does not require user interaction but does require the attacker to have valid authentication credentials, which may limit the attack surface to authorized users or compromised accounts. The CVSS 4.0 base score of 8.6 reflects the high impact on confidentiality and integrity, with low attack complexity and no user interaction needed. The vulnerability has been addressed in AVideo version 22.0 by implementing proper validation and allow-listing of URLs to prevent arbitrary server-side requests. No known exploits are currently reported in the wild, but the potential for significant impact exists given the nature of SSRF attacks and the sensitive data that may be exposed.
Potential Impact
The SSRF vulnerability in AVideo can have severe consequences for organizations using affected versions. By exploiting this flaw, an attacker with valid credentials can access internal network resources that are normally protected from external access. This can lead to unauthorized disclosure of sensitive information such as internal APIs, metadata services, or configuration data. In some deployment environments, SSRF can be a stepping stone for further compromise, including privilege escalation, lateral movement, or execution of unauthorized commands if internal services are vulnerable. The impact is heightened in cloud or containerized environments where metadata services provide critical instance or credential information. Additionally, the compromise of internal services may disrupt availability or integrity of video platform operations. Organizations relying on AVideo for video hosting or streaming may face data breaches, service disruptions, or reputational damage if this vulnerability is exploited. The requirement for authentication reduces the risk somewhat but does not eliminate it, especially if user credentials are weak, reused, or compromised.
Mitigation Recommendations
To mitigate CVE-2026-27732, organizations should upgrade all AVideo instances to version 22.0 or later, where the vulnerability is fixed. Until upgrades can be applied, implement strict network segmentation and firewall rules to restrict the AVideo server's outbound HTTP requests, limiting them only to trusted external resources. Employ allow-listing at the network or application level to prevent server-side requests to internal IP ranges or sensitive endpoints. Monitor and audit authenticated user activity for unusual patterns that could indicate SSRF exploitation attempts. Enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. Additionally, review and harden internal services that could be targeted via SSRF, such as metadata services or internal APIs, by implementing authentication and access controls. Consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities to detect and block malicious requests. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Japan, South Korea, India, Brazil, Netherlands, Sweden
CVE-2026-27732: CWE-918: Server-Side Request Forgery (SSRF) in WWBN AVideo
Description
WWBN AVideo is an open source video platform. Prior to version 22.0, the `aVideoEncoder.json.php` API endpoint accepts a `downloadURL` parameter and fetches the referenced resource server-side without proper validation or an allow-list. This allows authenticated users to trigger server-side requests to arbitrary URLs (including internal network endpoints). An authenticated attacker can leverage SSRF to interact with internal services and retrieve sensitive data (e.g., internal APIs, metadata services), potentially leading to further compromise depending on the deployment environment. This issue has been fixed in AVideo version 22.0.
AI-Powered Analysis
Technical Analysis
CVE-2026-27732 is a Server-Side Request Forgery (SSRF) vulnerability identified in WWBN's open-source video platform, AVideo, specifically in versions prior to 22.0. The vulnerability resides in the aVideoEncoder.json.php API endpoint, which accepts a parameter named downloadURL. This parameter is used by the server to fetch external resources without adequate validation or an allow-list mechanism. As a result, an authenticated attacker can manipulate this parameter to force the server to initiate HTTP requests to arbitrary URLs, including internal network addresses that are typically inaccessible externally. This SSRF flaw can be leveraged to interact with internal services such as metadata services, internal APIs, or other sensitive endpoints, potentially exposing confidential information or enabling lateral movement within the network. The vulnerability does not require user interaction but does require the attacker to have valid authentication credentials, which may limit the attack surface to authorized users or compromised accounts. The CVSS 4.0 base score of 8.6 reflects the high impact on confidentiality and integrity, with low attack complexity and no user interaction needed. The vulnerability has been addressed in AVideo version 22.0 by implementing proper validation and allow-listing of URLs to prevent arbitrary server-side requests. No known exploits are currently reported in the wild, but the potential for significant impact exists given the nature of SSRF attacks and the sensitive data that may be exposed.
Potential Impact
The SSRF vulnerability in AVideo can have severe consequences for organizations using affected versions. By exploiting this flaw, an attacker with valid credentials can access internal network resources that are normally protected from external access. This can lead to unauthorized disclosure of sensitive information such as internal APIs, metadata services, or configuration data. In some deployment environments, SSRF can be a stepping stone for further compromise, including privilege escalation, lateral movement, or execution of unauthorized commands if internal services are vulnerable. The impact is heightened in cloud or containerized environments where metadata services provide critical instance or credential information. Additionally, the compromise of internal services may disrupt availability or integrity of video platform operations. Organizations relying on AVideo for video hosting or streaming may face data breaches, service disruptions, or reputational damage if this vulnerability is exploited. The requirement for authentication reduces the risk somewhat but does not eliminate it, especially if user credentials are weak, reused, or compromised.
Mitigation Recommendations
To mitigate CVE-2026-27732, organizations should upgrade all AVideo instances to version 22.0 or later, where the vulnerability is fixed. Until upgrades can be applied, implement strict network segmentation and firewall rules to restrict the AVideo server's outbound HTTP requests, limiting them only to trusted external resources. Employ allow-listing at the network or application level to prevent server-side requests to internal IP ranges or sensitive endpoints. Monitor and audit authenticated user activity for unusual patterns that could indicate SSRF exploitation attempts. Enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. Additionally, review and harden internal services that could be targeted via SSRF, such as metadata services or internal APIs, by implementing authentication and access controls. Consider deploying Web Application Firewalls (WAFs) with SSRF detection capabilities to detect and block malicious requests. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-23T18:37:14.789Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 699e0f3fbe58cf853b290da4
Added to database: 2/24/2026, 8:51:11 PM
Last enriched: 2/24/2026, 9:02:10 PM
Last updated: 2/25/2026, 12:00:20 AM
Views: 4
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.
Related Threats
CVE-2026-3134: SQL Injection in itsourcecode News Portal Project
MediumCVE-2026-3133: SQL Injection in itsourcecode Document Management System
MediumCVE-2026-27593: CWE-640: Weak Password Recovery Mechanism for Forgotten Password in statamic cms
CriticalCVE-2026-27117: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in rikyoz bit7z
MediumCVE-2026-27572: CWE-770: Allocation of Resources Without Limits or Throttling in bytecodealliance wasmtime
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.