CVE
WWBN AVideo 14.3 through 29.7.1 Stored XSS via Video Source Tag
Affects WWBN AVideo 14.3 through 29.7.1 and current master as of the advisory, where accounts with upload permission can plant the script. No vendor rating or fixed version is listed in the facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attacker must be an authenticated user with upload permission (User::canUpload()). Affected versions 14.3 through 29.7.1 and current master as of the advisory.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Stored cross-site scripting in WWBN AVideo lets a user with low-privilege login (an uploader) plant script code that runs when a user interacts with the affected page, such as an administrator viewing it. An attacker who gets an administrator to act can use that session to install a plugin archive containing PHP code. The flaw is reached remotely over the network, but it requires the victim to take an action.
Read the original description
WWBN AVideo 14.3 through 29.7.1 contains a stored cross-site scripting vulnerability that allows uploaders to inject scripts via the videoDownloadedLink value stored unescaped through objects/aVideoEncoder.json.php. Attackers can embed event-handler payloads in the URL host rendered as a Source tag in view/managerVideos_body.php, executing in administrator sessions to install plugin archives containing PHP.
Who should check
Teams running WWBN AVideo versions 14.3 through 29.7.1, or current master, especially those with uploader accounts and administrators or video moderators using the video manager.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Attacker must be an authenticated user with upload permission (User::canUpload()). Affected versions 14.3 through 29.7.1 and current master as of the advisory.Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126806 (WWBN AVideo 14.3 through 29.7.1 Stored XSS via Video Source Tag), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126806 (entry last updated 2026-11-11):
Affected:
- WWBN AVideo: from 14.3, through 29.7.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Attacker must be an authenticated user with upload permission (User::canUpload()). (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-2qq6-qfcq-jmr9)
- Affected versions 14.3 through 29.7.1 and current master as of the advisory. (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-2qq6-qfcq-jmr9)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-126806 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126806 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/WWBN/AVideo/security/advisories/GHSA-2qq6-qfcq-jmr9
- https://github.com/WWBN/AVideo/commit/da1da205608d57b1e695a7fad8288a2f5f9a0e0f
- https://github.com/WWBN/AVideo/blob/v29.7.1/objects/functionTags.php#L198-L221
- https://github.com/WWBN/AVideo/blob/v29.7.1/view/managerVideos_body.php#L1997-L2011
- https://www.vulncheck.com/advisories/wwbn-avideo-14.3-through-29.7.1-stored-xss-via-video-source-tag
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126806
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126806"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- WWBN AVideo
From 14.3 · through 29.7.1
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126806
Is CVE-2026-126806 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The script is stored in a video source tag and runs in the browser of an administrator or video moderator on the AVideo site. The advisory says it can read the page's CSRF token and perform admin actions, such as creating an admin account, changing settings, or uploading a plugin ZIP containing PHP, which could lead to remote code execution.Source: github.com
Which versions are affected by CVE-2026-126806?
AVideo: from 14.3 through 29.7.1.Source: cve.now feed data
Am I affected, and how do I check?
The advisory lists AVideo 14.3 through 29.7.1 and current master as of the advisory. The attacker needs an authenticated account with upload permission (User::canUpload()). To check a installation, compare its AVideo version with that range.Source: github.com
How do I fix CVE-2026-126806?
The facts do not name a fixed version, so no upgrade target can be given from them. Check the vendor's advisory or project releases for a patched version and apply it when available.Source: github.com