/

CVE-2026-77615

Severity:

HIGH RISK

(8.7)

Cross-Site Scripting (CWE-79) in Paella Player Web UI

CVE-2026-77615

Deferred

Vulnerability type

Category:

Cross-Site Scripting

CWE:

CWE-79

Impact:

Client-Side Code Execution

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

A high-severity cross-site scripting vulnerability in Paella Player allows malicious closed-caption cue text to be interpreted as active content when displayed by the video player. The issue becomes risky when an attacker can influence caption data that is later rendered in a viewer's browser.

Affected context

The vulnerability occurs in Paella Player deployments that render closed-caption cue text without adequately treating it as untrusted content. It may affect applications embedding vulnerable Paella Player libraries, including Opencast environments that use affected Paella Player releases. Exploitability depends on whether an attacker can create, modify, or supply caption data that reaches the player.

Exploit preconditions

  • Attack surface: Web-based video playback and caption rendering
  • Required access: Ability to influence closed-caption or subtitle content, directly or through an upstream content-management workflow
  • Trigger point: Rendering of attacker-controlled cue text in a user's browser
  • Why exploitation is possible: Caption content is not sufficiently constrained or output-encoded before being inserted into the document

Why this happens

The underlying bug is improper neutralization of user-controlled input in a web page context. When closed-caption cue text is treated as trusted markup rather than plain text, browser interpretation may allow injected script-capable content to execute. This maps to CWE-79: Improper Neutralization of Input During Web Page Generation, commonly known as cross-site scripting.

Potential impact

  • Arbitrary script execution in a viewer's browser session
  • Theft of accessible session data or page content
  • Unauthorized actions performed through the affected application
  • Defacement or manipulation of the video-player interface
  • Phishing or redirection to attacker-controlled content

General mitigation guidance

Mitigation generally focuses on ensuring that caption data remains inert throughout its processing and rendering lifecycle.

Common defensive patterns include:

  • Treating cue text as text rather than trusted HTML
  • Applying context-appropriate output encoding at the rendering boundary
  • Sanitizing markup with a restrictive, allowlist-based policy when formatted captions are required
  • Validating caption files and metadata before publication
  • Restricting who can create or modify caption content
  • Applying a restrictive Content Security Policy as defense in depth
  • Limiting application privileges and exposed session capabilities

How teams detect issues like this

Organizations can identify related issues through:

  • Static analysis rules for unsafe DOM insertion and template rendering
  • Code review checks for caption or subtitle text inserted as HTML
  • Tests using representative markup and script-like input in cue text
  • Content-management policies that require validation and review of uploaded captions
  • Browser security telemetry and application logs for unexpected caption content or client-side errors

Automated security review tools may help flag unsafe rendering patterns, but results should be confirmed against the application's actual output context.

Sources

SourceLink
github.comgithub.com/opencast/opencast/commit/701682c635f668228c3e8fb7b4564b3294788e40
github.comgithub.com/opencast/opencast/pull/7736
github.comgithub.com/opencast/opencast/releases/tag/19.7
github.comgithub.com/opencast/opencast/releases/tag/20.2
github.comgithub.com/opencast/opencast/security/advisories/GHSA-m6c8-jcw2-5r25
github.comgithub.com/polimediaupv/paella-core/commit/94a36490808ac5a1f60a0745d71ec9253f6d206b
github.comgithub.com/polimediaupv/paella-core/commit/9b2f14ec4cf55efaf4c045c77a5ed8f5ec559ab4
github.comgithub.com/polimediaupv/paella-player/blob/a1b6c42467938a00a4b4d0b8c68435cd4f9d2a16/repos/paella-core/CHANGELOG.md?plain=1#L21
github.comgithub.com/polimediaupv/paella-player/commit/6fe4af7306044198c8e91e2e7f4128428b83cf03

Frequently asked

questions

It can be, when an attacker can influence caption content through a remotely accessible upload, authoring, or content-management workflow and that content is viewed by another user.

Not necessarily. The required access depends on how captions are created and distributed; an authenticated content contributor may be sufficient in deployments that restrict caption management.

Render closed-caption cue text as inert text by default, applying context-aware output encoding and restrictive sanitization only when intentionally supported formatting is required.

Combine input validation, safe rendering APIs, caption-content review controls, security-focused tests, and a restrictive Content Security Policy.

Find out what's already
exploitable in your codebase.