CVE-2026-34394: CWE-352: Cross-Site Request Forgery (CSRF) in WWBN AVideo
CVE-2026-34394 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability affecting WWBN AVideo versions 26. 0 and earlier. The vulnerability exists because the admin plugin configuration endpoint lacks CSRF token validation, allowing attackers to forge cross-origin POST requests. Due to the application's SameSite=None cookie policy and the plugins table bypassing standard access controls, attackers can overwrite critical plugin settings without authentication. This can lead to full platform takeover by reconfiguring payment processors, authentication providers, and cloud storage credentials. No patches are currently available, and exploitation requires victim administrator interaction via a malicious webpage. The CVSS score is 8. 1, reflecting high confidentiality and integrity impact with no availability impact. Organizations using AVideo should implement strict network controls and monitor administrative actions until a patch is released.
AI Analysis
Technical Summary
WWBN AVideo, an open-source video platform, suffers from a critical CSRF vulnerability (CVE-2026-34394) in its admin plugin configuration endpoint (admin/save.json.php) in versions 26.0 and prior. The endpoint processes POST requests to modify plugin settings but does not perform any CSRF token validation, as it lacks calls to isGlobalTokenValid() or verifyToken(). This absence of anti-CSRF protections, combined with the platform's explicit SameSite=None cookie policy, enables attackers to craft malicious cross-origin POST requests that execute in the context of an authenticated administrator's browser session. Furthermore, the plugins table is included in the ignoreTableSecurityCheck() array, which bypasses standard table-level access controls, allowing unauthorized modification of plugin configurations. Exploiting this vulnerability, an attacker can overwrite sensitive settings such as payment processor configurations, authentication provider credentials, and cloud storage access details, effectively gaining full control over the platform's functionality. The vulnerability does not require prior authentication but does require the victim administrator to visit a malicious webpage that triggers the forged request. At the time of disclosure, no patches or official mitigations have been released, increasing the risk for affected deployments. The CVSS v3.1 base score is 8.1, indicating high severity due to the ease of exploitation, high impact on confidentiality and integrity, and the broad scope of affected systems running vulnerable AVideo versions.
Potential Impact
The impact of CVE-2026-34394 is significant for organizations using WWBN AVideo as their video platform. Successful exploitation allows attackers to fully compromise platform functionality by modifying critical plugin settings without authentication. This can lead to unauthorized changes in payment processing configurations, potentially redirecting funds or enabling fraud. Altering authentication provider settings could allow attackers to bypass user authentication or escalate privileges. Manipulating cloud storage credentials may expose sensitive media content or enable data exfiltration. The compromise of these components undermines the confidentiality and integrity of the platform and its data, potentially causing reputational damage, financial loss, and operational disruption. Since the vulnerability requires victim administrator interaction, targeted spear-phishing or social engineering attacks could be used to induce the administrator to visit malicious sites. The lack of available patches increases exposure time, making timely detection and mitigation critical. Organizations with public-facing AVideo instances or those with multiple administrators are at higher risk, as the attack surface and likelihood of successful exploitation increase.
Mitigation Recommendations
Until an official patch is released, organizations should implement several specific mitigations to reduce risk. First, restrict administrative access to the AVideo platform via network segmentation and IP whitelisting to limit exposure to trusted users only. Second, deploy web application firewalls (WAFs) with custom rules to detect and block suspicious cross-origin POST requests targeting admin/save.json.php. Third, educate administrators to avoid visiting untrusted websites while logged into the platform to prevent CSRF attack vectors. Fourth, consider temporarily disabling or limiting plugin configuration changes if feasible. Fifth, enable multi-factor authentication (MFA) for administrator accounts to reduce the impact of compromised credentials. Sixth, monitor logs for unusual administrative activity, such as unexpected plugin configuration changes or authentication provider modifications. Finally, maintain regular backups of configuration data to enable recovery in case of compromise. Organizations should prioritize patching as soon as a fix becomes available and validate that CSRF protections are properly implemented in the admin interface.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2026-34394: CWE-352: Cross-Site Request Forgery (CSRF) in WWBN AVideo
Description
CVE-2026-34394 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability affecting WWBN AVideo versions 26. 0 and earlier. The vulnerability exists because the admin plugin configuration endpoint lacks CSRF token validation, allowing attackers to forge cross-origin POST requests. Due to the application's SameSite=None cookie policy and the plugins table bypassing standard access controls, attackers can overwrite critical plugin settings without authentication. This can lead to full platform takeover by reconfiguring payment processors, authentication providers, and cloud storage credentials. No patches are currently available, and exploitation requires victim administrator interaction via a malicious webpage. The CVSS score is 8. 1, reflecting high confidentiality and integrity impact with no availability impact. Organizations using AVideo should implement strict network controls and monitor administrative actions until a patch is released.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
WWBN AVideo, an open-source video platform, suffers from a critical CSRF vulnerability (CVE-2026-34394) in its admin plugin configuration endpoint (admin/save.json.php) in versions 26.0 and prior. The endpoint processes POST requests to modify plugin settings but does not perform any CSRF token validation, as it lacks calls to isGlobalTokenValid() or verifyToken(). This absence of anti-CSRF protections, combined with the platform's explicit SameSite=None cookie policy, enables attackers to craft malicious cross-origin POST requests that execute in the context of an authenticated administrator's browser session. Furthermore, the plugins table is included in the ignoreTableSecurityCheck() array, which bypasses standard table-level access controls, allowing unauthorized modification of plugin configurations. Exploiting this vulnerability, an attacker can overwrite sensitive settings such as payment processor configurations, authentication provider credentials, and cloud storage access details, effectively gaining full control over the platform's functionality. The vulnerability does not require prior authentication but does require the victim administrator to visit a malicious webpage that triggers the forged request. At the time of disclosure, no patches or official mitigations have been released, increasing the risk for affected deployments. The CVSS v3.1 base score is 8.1, indicating high severity due to the ease of exploitation, high impact on confidentiality and integrity, and the broad scope of affected systems running vulnerable AVideo versions.
Potential Impact
The impact of CVE-2026-34394 is significant for organizations using WWBN AVideo as their video platform. Successful exploitation allows attackers to fully compromise platform functionality by modifying critical plugin settings without authentication. This can lead to unauthorized changes in payment processing configurations, potentially redirecting funds or enabling fraud. Altering authentication provider settings could allow attackers to bypass user authentication or escalate privileges. Manipulating cloud storage credentials may expose sensitive media content or enable data exfiltration. The compromise of these components undermines the confidentiality and integrity of the platform and its data, potentially causing reputational damage, financial loss, and operational disruption. Since the vulnerability requires victim administrator interaction, targeted spear-phishing or social engineering attacks could be used to induce the administrator to visit malicious sites. The lack of available patches increases exposure time, making timely detection and mitigation critical. Organizations with public-facing AVideo instances or those with multiple administrators are at higher risk, as the attack surface and likelihood of successful exploitation increase.
Mitigation Recommendations
Until an official patch is released, organizations should implement several specific mitigations to reduce risk. First, restrict administrative access to the AVideo platform via network segmentation and IP whitelisting to limit exposure to trusted users only. Second, deploy web application firewalls (WAFs) with custom rules to detect and block suspicious cross-origin POST requests targeting admin/save.json.php. Third, educate administrators to avoid visiting untrusted websites while logged into the platform to prevent CSRF attack vectors. Fourth, consider temporarily disabling or limiting plugin configuration changes if feasible. Fifth, enable multi-factor authentication (MFA) for administrator accounts to reduce the impact of compromised credentials. Sixth, monitor logs for unusual administrative activity, such as unexpected plugin configuration changes or authentication provider modifications. Finally, maintain regular backups of configuration data to enable recovery in case of compromise. Organizations should prioritize patching as soon as a fix becomes available and validate that CSRF protections are properly implemented in the admin interface.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-27T13:45:29.619Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69cc343ee6bfc5ba1d4033d2
Added to database: 3/31/2026, 8:53:18 PM
Last enriched: 3/31/2026, 9:08:21 PM
Last updated: 3/31/2026, 9:55:50 PM
Views: 2
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.
External Links
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.