/

CVE-2026-89256

Severity:

HIGH RISK

(8.7)

Stored XSS (CWE-79) in AVideo Bookmark Plugin HTML

CVE-2026-89256

Deferred

Vulnerability type

Category:

Stored Cross-Site Scripting

CWE:

CWE-79

Impact:

Client-Side Code Execution and Session Compromise

Severity:

HIGH RISK

(8.7)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

CVE-2026-89256 is a high-severity stored cross-site scripting vulnerability in AVideo's Bookmark plugin. A video owner may store an unencoded chapter name that is later inserted into public watch-page HTML, causing scripts to execute in the AVideo origin for visitors who view the affected video.

Affected context

The vulnerability occurs in AVideo deployments using the Bookmark plugin when chapter names are accepted from video-owner-controlled input and later concatenated into public watch-page HTML without context-appropriate output encoding. Risk depends on the affected video being accessible to visitors and the injected content being rendered by their browsers.

Exploit preconditions

  • Attack surface: Bookmark chapter-name input and the public video watch page
  • Required access: The ability to manage or edit bookmarks for a video, typically as the video owner
  • Trigger point: A visitor loads the affected video's public watch page
  • Why exploitation is possible: Untrusted chapter-name content is inserted into HTML without sufficient output encoding, allowing browser-interpreted script content to persist

Why this happens

The underlying bug is a failure to encode untrusted data before embedding it in an HTML response. The Bookmark plugin treats a chapter name as ordinary markup content even though it can be controlled by a video owner, allowing the browser to interpret attacker-supplied characters as active client-side content. This behavior maps to CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), specifically a stored XSS pattern.

Potential impact

  • Malicious scripts could execute in visitors' AVideo-origin browser contexts
  • Session information or accessible account data could be exposed
  • Visitors could be redirected to deceptive or harmful content
  • Unauthorized actions could be performed through a victim's authenticated session
  • Trust in public video pages could be damaged

General mitigation guidance

Mitigation generally focuses on treating all user-controlled chapter metadata as untrusted and applying context-appropriate output encoding at the point of HTML generation.

Common defensive patterns include:

  • Encode chapter names for the exact output context rather than relying only on input filtering
  • Prefer safe DOM or templating APIs that separate data from markup
  • Apply strict allowlists and schema validation to bookmark metadata
  • Use a restrictive Content Security Policy as defense in depth
  • Limit authoring privileges and review who can modify publicly visible video metadata
  • Avoid rendering user-controlled values as raw HTML by default

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis rules identifying string concatenation of request or metadata values into HTML
  • Code review checks for missing output encoding in templates and response builders
  • Tests that submit HTML-significant characters in bookmark and chapter fields and verify they render as text
  • Content Security Policy reporting for unexpected script execution or violations
  • Runtime monitoring of unusual changes to public video metadata and suspicious browser-side behavior

Automated security review tools may help identify unsafe HTML construction, but findings should be validated against the rendering context and framework behavior.

Sources

SourceLink
github.comgithub.com/WWBN/AVideo/security/advisories/GHSA-jggq-mm5m-r5wv
vulncheck.comvulncheck.com/advisories/avideo-bookmark-plugin-stored-xss-via-chapter-names

Frequently asked

questions

It can affect visitors remotely through a public video page, but exploitation generally requires an authorized video owner or another principal able to modify the affected bookmark data.

Any visitor whose browser renders the affected video's watch page may be exposed, with the exact scope depending on page visibility and access controls.

Treat chapter names as untrusted text and apply context-appropriate HTML output encoding, while avoiding raw HTML rendering for user-controlled values.

Combine secure templating or DOM APIs, input validation, output encoding, automated security tests, restrictive browser policies, and least-privilege metadata management.

Find out what's already
exploitable in your codebase.