VulnerabilityPublished 23 Mar 2026

CVE-2026-33649: WWBN AVideo · Cross-Site Request Forgery (CSRF)

Affects WWBN AVideoSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.1 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

8.1High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 23 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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 <=26.0	Fixed in–
GitHubwwbn/AVideo`pkg:github/wwbn/AVideo`Other threats	Affected <=26.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

Until an official patch is released, organizations should implement several specific mitigations: 1) Restrict administrative access to trusted networks or VPNs to reduce exposure to external CSRF attempts. 2) Educate administrators to avoid visiting untrusted or suspicious websites while logged into the AVideo platform. 3) Employ web application firewalls (WAFs) to detect and block suspicious requests to the vulnerable endpoint, especially those originating from cross-site contexts or containing unusual GET parameters. 4) Modify server or application configurations to enforce stricter SameSite cookie policies (e.g., SameSite=Lax or Strict) if feasible, to prevent cookies from being sent on cross-site requests. 5) Implement additional authentication or confirmation steps for permission changes, such as requiring re-authentication or out-of-band verification. 6) Monitor logs for unusual permission changes or access patterns indicative of exploitation attempts. 7) Consider isolating or disabling the vulnerable endpoint temporarily if it is not critical to operations. These targeted actions go beyond generic advice and address the specific mechanics of this CSRF vulnerability.

Description

CVE-2026-33649 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in WWBN AVideo versions up to 26.0. The vulnerability exists because the `plugin/Permissions/setPermission.json.php` endpoint accepts GET requests to change user group permissions without CSRF token validation. Additionally, the application sets session cookies with SameSite=None, allowing cross-site requests to carry session cookies. An unauthenticated attacker can craft a malicious webpage containing image tags that trigger permission changes when visited by an admin user, effectively escalating the attacker's privileges to near-admin level. No patches are currently available. Exploitation requires the admin to visit the attacker-controlled page but no authentication or user interaction beyond page visit is needed. The CVSS score is 8.

Impact

The impact of CVE-2026-33649 is significant for organizations using WWBN AVideo, especially those relying on it for managing video content and user permissions. Successful exploitation allows an unauthenticated attacker to escalate privileges by granting their user group arbitrary permissions, effectively gaining near-administrative control over the platform. This can lead to unauthorized access to sensitive video content, manipulation or deletion of videos, alteration of user roles, and potential disruption of service. Confidentiality is severely compromised as attackers can access restricted content, and integrity is undermined by unauthorized permission changes. Availability impact is minimal but could occur indirectly if attackers disrupt administrative functions. Given the ease of exploitation—requiring only that an admin visit a malicious page—and the lack of authentication barriers, the threat is acute. Organizations with multiple administrators or those with high-value content are at elevated risk. The absence of a patch increases exposure duration, potentially inviting targeted attacks once exploit code becomes public.

CWE-352Cross-Site Request Forgery (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/WWBN/AVideo/security/advisories/GHSA-g8x9-7mgh-7cvj (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Mar 2026, 20:37 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats