Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77615 high CVSS 8.7

Cross-Site Scripting (XSS) in org.opencastproject:opencast-engage-paella-player-7 (CVE-2026-77615)

Summary

Cross-site scripting in org.opencastproject:opencast-engage-paella-player-7 (CVE-2026-77615). Confidential information can be exposed externally. Exploitable via GET /search/episode.json. Mitigation: upgrade to 20.2 or later.

Original description

The description as published by the source.

Summary

The Opencast Paella player renders caption cue text into innerHTML without escaping. The captions canvas clears _captionsContainer.innerHTML and then appends each active cue with _captionsContainer.innerHTML += cue, so HTML inside a WebVTT or DFXP cue becomes live DOM and executes in the Opencast origin.

The caption track is read from any media package element with a captions/* flavor and is served, with the player manifest, to anonymous viewers through /search/episode.json. The caption plugins that consume it are enabled in the default player configuration, the "Subtitles" upload that produces a captions/source track is active by default, and no caption processing step escapes the cue text.

A user who can upload a subtitle to an event and publish it stores the payload in the published caption file. Any viewer who opens the event and turns captions on runs the script.

Result: a non-admin content author stores JavaScript in a subtitle cue that executes in the browser session of every viewer who enables captions on that event, including anonymous viewers and authenticated staff.

Affected

opencast/opencast, engage-paella-player module. Supported release lines 19.x and 20.x are affected (and 18.x). Live-confirmed on 18.8 (Paella 7, paella-core 1.50.2) and 20.0 (Paella 8, paella-core 1.50.4); 19.5 ships the code-identical caption path (paella-core 1.50.4, same EpisodeConversor and default plugin config as 20.0). The captions canvas uses the same…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-77615 has been found in org.opencastproject:opencast-engage-paella-player-7.
Attackers can target a specific entry point like GET /search/episode.json over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade org.opencastproject:opencast-engage-paella-player-7 to 20.2 or later.
If unsure, ask your IT team or search "org.opencastproject:opencast-engage-paella-player-7 CVE-2026-77615" on the vendor's site.

CVE-2026-77615 (org.opencastproject:opencast-engage-paella-player-7) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: GET /search/episode.json / innerHTML / _captionsContainer.innerHTML / EpisodeConversor
Patched: 20.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in org.opencastproject:opencast-engage-paella-player-7. Attackers reach the vulnerable code path via GET /search/episode.json.

📍 Affected scope

Check the vendor advisory for the affected versions of org.opencastproject:opencast-engage-paella-player-7. Attack surface: GET /search/episode.json / innerHTML / _captionsContainer.innerHTML / EpisodeConversor.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 20.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /search/episode.json requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.opencastproject:opencast-engage-paella-player-7 を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /search/episode.json' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /search/episode.json への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade org.opencastproject:opencast-engage-paella-player-7 to 20.2

    ステージング環境で 20.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /search/episode.json on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.opencastproject:opencast-engage-paella-player-7
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.2"}]}]
npm paella-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.50.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details