CVE
AVideo stored XSS in embed video iframe src
Affects WWBN AVideo from 6.5 through 29.8.0, only for embed-type videos where the attacker holds canUpload permission. No fixed version is listed in the checked facts.
- Exploited
- Proof of concept public, per CISA
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The video's type is embed. The attacker has an account with upload permission (canUpload).
Summary
WWBN AVideo has a stored cross-site scripting flaw in its embed video feature. A user with upload permission can submit a javascript: video link that runs in the browser of anyone who views the embed, including administrators, which can be used to create new administrator accounts. The attack is carried out over the network, and a viewer must take an action such as opening the embed.
Original description
WWBN AVideo from 6.5 contains a stored cross-site scripting vulnerability that allows users with upload permission to inject script by submitting a javascript: scheme videoLink for embed videos. The unvalidated URL is rendered into an iframe src in videoEmbeded.php and PlayerSkins.php, executing for viewers including administrators and enabling creation of new administrator accounts.
Who should check
Teams running WWBN AVideo 6.5 or later with video upload enabled, where embed videos render a stored video link into an iframe.
Not fixed by: Patching only new writes leaves existing payloads firing.
“Present since 9c27730 (6.5), which added the embed iframe.”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 45 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The video's type is embed. The attacker has an account with upload permission (canUpload).Workaround: The checked facts name no workaround. The planting step depends on the canUpload permission, so reviewing which accounts hold that permission is the one step the facts point to.
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-130648 (WWBN AVideo from 6.5 Stored XSS via Embed Video videoLink iframe src), 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-130648 (entry last updated 2026-11-18):
Affected:
- WWBN AVideo: from 6.5, through 29.8.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The video's type is embed. (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-vq8m-9xp3-76fg)
- The attacker has an account with upload permission (canUpload). (source: https://github.com/WWBN/AVideo/security/advisories/GHSA-vq8m-9xp3-76fg)
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-130648 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130648 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-vq8m-9xp3-76fg
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-130648
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-130648"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- WWBN AVideo
From 6.5 · through 29.8.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · WWBN/AVideo · Advisory GHSA-vq8m-9xp3-76fg |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130648 |
| Record | NVD · CVE-2026-130648 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130648
Is CVE-2026-130648 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The Embed Video videoLink iframe src field stores a script that runs in the site's origin for every viewer of the video, including administrators, and acts as whoever is viewing. When the viewer is an administrator, the script can create a second administrator account.Source: github.com
Which versions are affected by CVE-2026-130648?
AVideo: from 6.5 through 29.8.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 6.5 through 29.8.0 are in the affected range, and only videos whose type is embed are involved. Planting the script requires an account with upload permission (canUpload). Compare the AVideo version and the video type against these conditions to see whether a given site falls in scope.Source: github.com
How do I fix CVE-2026-130648?
The checked facts do not name a fixed version or vendor patch identifiers, so no upgrade target can be given from them. Check the vendor's advisory for a fixed release or patch before relying on any update.Source: github.com
What if there's no patch?
The checked facts name no workaround. The planting step depends on the canUpload permission, so reviewing which accounts hold that permission is the one step the facts point to.Source: github.com