Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33507: CWE-352: Cross-Site Request Forgery (CSRF) in WWBN AVideo

0
High
VulnerabilityCVE-2026-33507cvecve-2026-33507cwe-352
Published: Mon Mar 23 2026 (03/23/2026, 16:32:28 UTC)
Source: CVE Database V5
Vendor/Project: WWBN
Product: AVideo

Description

CVE-2026-33507 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in WWBN AVideo versions up to 26. 0. The vulnerability exists in the plugin import endpoint, which allows authenticated admin users to upload and install plugin ZIP files containing executable PHP code without any CSRF protection. Due to the application setting session cookies with SameSite=None for HTTPS, an attacker can craft a malicious webpage that, when visited by an authenticated admin, silently uploads a plugin with a PHP webshell, enabling remote code execution (RCE) on the server. This flaw requires user interaction (the admin visiting the malicious page) but no prior authentication by the attacker. A patch has been committed to fix this issue. The CVSS score is 8. 8, reflecting high impact on confidentiality, integrity, and availability.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/23/2026, 17:16:15 UTC

Technical Analysis

WWBN AVideo is an open-source video platform that, in versions up to and including 26.0, contains a critical CSRF vulnerability (CVE-2026-33507) in the `objects/pluginImport.json.php` endpoint. This endpoint allows admin users to upload ZIP files containing plugins, which can include executable PHP code. The vulnerability arises because this endpoint lacks any CSRF protection mechanisms, such as anti-CSRF tokens or same-origin checks. Additionally, the application explicitly sets the session cookie attribute `SameSite=None` for HTTPS connections, which allows cookies to be sent with cross-site requests. An attacker can exploit this by crafting a malicious webpage that, when visited by an authenticated admin, triggers a silent POST request to the vulnerable endpoint, uploading a malicious plugin containing a PHP webshell. This results in remote code execution on the server with admin privileges. The attacker does not need to be authenticated but relies on the admin visiting the malicious page, making user interaction necessary. The vulnerability impacts confidentiality, integrity, and availability of the affected servers. A patch has been committed (commit d1bc1695edd9ad4468a48cea0df6cd943a2635f3) to address this issue by adding CSRF protections.

Potential Impact

The exploitation of this vulnerability allows attackers to achieve remote code execution on servers running vulnerable versions of WWBN AVideo, leading to full compromise of the affected system. Attackers can execute arbitrary PHP code, potentially leading to data theft, defacement, malware deployment, lateral movement within networks, and disruption of video services. Given that the vulnerability requires an admin user to visit a malicious page, social engineering or targeted phishing campaigns could be used to trigger the exploit. The impact extends to confidentiality (exposure of sensitive video content and user data), integrity (modification or deletion of content and system files), and availability (service disruption or denial of service). Organizations relying on AVideo for video hosting or streaming services face significant operational and reputational risks if exploited.

Mitigation Recommendations

1. Immediately update WWBN AVideo to the latest patched version that includes the fix for CVE-2026-33507. 2. If patching is not immediately possible, implement web application firewall (WAF) rules to detect and block unauthorized POST requests to the `pluginImport.json.php` endpoint. 3. Restrict administrative access to trusted networks or VPNs to reduce exposure to phishing attacks. 4. Educate administrators about the risks of visiting untrusted websites while logged into admin accounts. 5. Review and harden session cookie settings, considering setting `SameSite` to `Lax` or `Strict` where feasible to prevent cross-site requests. 6. Monitor server logs for unusual plugin uploads or webshell activity. 7. Employ multi-factor authentication (MFA) for admin accounts to reduce risk from compromised credentials. 8. Conduct regular security audits and penetration testing focusing on admin interfaces and plugin management functionalities.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-20T16:59:08.888Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69c171cff4197a8e3b777515

Added to database: 3/23/2026, 5:01:03 PM

Last enriched: 3/23/2026, 5:16:15 PM

Last updated: 3/23/2026, 6:04:58 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses