Skip to content
Unrated

Cross-Site Scripting (XSS) in beets

CVE-2026-42052 First seen on SecPulse

Summary

Cross-site scripting in beets (CVE-2026-42052). Risk of unauthorized operations or information disclosure. Exploitable via title. Mitigation: upgrade to 2.10.0 or later.

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-42052 has been found in beets.
Attackers can target a specific entry point like title over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade beets to 2.10.0 or later.
If unsure, ask your IT team or search "beets CVE-2026-42052" on the vendor's site.

CVE-2026-42052 (beets) — CWE-79
Attack surface: title / lyrics / comments
Patched: 2.10.0 — 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 beets. Attackers reach the vulnerable code path via title.

Affected scope

Check the vendor advisory for the affected versions of beets. Attack surface: title / lyrics / comments.

Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

How to fix

Update to 2.10.0.

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 request patterns matching this CVE's known IOCs. Run grep -r 'beets' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposureidentify
    grep -r 'beets' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で beets を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patchpatch
    Upgrade beets to 2.10.0

    ステージング環境で 2.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

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

Affected packages

EcosystemPackageAffectedFixed
pip beets
< 2.10.0
2.10.0
PyPI beets
< 2.10.0
2.10.0

Fix status by distribution

Fixed packages published by each distribution for this CVE

Original description The description as published by the source.

Beets is the media library management system. Prior to version 2.10.0, the bundled web UI uses Underscore template interpolation mode <%= ... %> for untrusted metadata fields. In this runtime, <%= ... %> is raw insertion and HTML escaping is only performed by <%- ... %>. Rendered output is then inserted with .html(...), allowing attacker-controlled markup to become active DOM. This issue has been patched in version 2.10.0.

Source: NIST National Vulnerability Database NVD GitHub Advisory

References

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