dbcve.org
AvideoApplication · Wwbn

CVE-2026-45580

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to after 29.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
WWBN AVideo is an open source video platform. In 29.0 and earlier, there is a stored cross-site scripting vulnerability. The Live plugin's "YouTube-style" view renders the live transmission's stream key into an HTML class attribute by raw echo, without htmlspecialchars(). A canStream user can persist a key containing " plus an event handler via plugin/Live/saveLive.php, and any visitor (logged in or anonymous) opening the stream's live page executes attacker JavaScript in the platform origin.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WWBN AVideo versions 29.0 and earlier contain a stored XSS vulnerability in the Live plugin's YouTube-style view. The stream key is rendered directly into an HTML class attribute without sanitization via htmlspecialchars(). A user with canStream permissions can inject JavaScript via plugin/Live/saveLive.php, which executes when any visitor views the live stream page.

MitigationApply htmlspecialchars() or equivalent output encoding to the stream key before rendering it into HTML class attributes in the Live plugin's view files. Sanitize all user-supplied data at output points.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AvideoApplication
Affected:<= 29.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check AVideo version
    Locate the version file or admin panel about page in your WWBN AVideo installation. Common paths include /VERSION.txt or the Admin Dashboard > About section.
    Affected if Your installed version is 29.0 or lower (the vulnerable version range).
  2. Verify Live plugin is installed
    Check the plugin directory for the Live plugin, typically in /plugin/Live/ within your AVideo installation. Alternatively, check via Admin Dashboard > Plugins to see if Live is listed as installed/enabled.
    Affected if The Live plugin is installed and enabled in your environment.
  3. Identify users with canStream privilege
    Access the Users management section in the AVideo admin panel. Look for users assigned the canStream role/permission, or inspect the users_table database for canStream=1.
    Affected if There exist users with canStream privileges who could inject malicious stream keys.
  4. Inspect stream key storage in database
    Query the live_stream_key table or relevant Live plugin database tables to examine stored stream key values. Look for any keys containing HTML or script tags, such as <script>, javascript:, or onload/onerror attributes.
    Affected if Any stream key records contain unsanitized HTML or JavaScript characters indicating a malicious payload has been stored.
  5. Check YouTube-style live view accessibility
    Navigate to the Live plugin's YouTube-style view page in your browser (typically /plugin/Live/?mode=YouTube or similar URL pattern). View the page source and search for the stream key value rendered in HTML class attributes.
    Affected if The stream key value appears in the HTML source without htmlspecialchars() encoding, meaning raw characters are visible in the markup.

You are affected if your AVideo version is 29.0 or earlier, the Live plugin is enabled, and either malicious stream keys are already stored in your database or the stream key renders unencoded in the YouTube-style live view HTML.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 29.0
Interim mitigation

Apply htmlspecialchars() or equivalent output encoding to the stream key before rendering it into HTML class attributes in the Live plugin's view files. Sanitize all user-supplied data at output points.

Fix this in Avideo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45580 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45580 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data