Cross-Site Scripting (XSS) in wlc (CVE-2026-42150)
Summary
Cross-site scripting in wlc (CVE-2026-42150). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.0.0 or later.
Original description
The description as published by the source.
wlc is a Weblate command-line client using Weblate's REST API. Prior to version 2.0.0, the HTML output format in wlc embeds API response data into HTML without escaping, allowing cross-site scripting when the output is rendered in a browser. This issue has been patched in version 2.0.0.
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-42150 has been found in wlc.
Risk of unauthorized operations or information disclosure. CVSS score: 5.1/10.
What to do: upgrade wlc to 2.0.0 or later.
If unsure, ask your IT team or search "wlc CVE-2026-42150" on the vendor's site.
CVE-2026-42150 (wlc) — CWE-79 / CVSS v3 5.1
Attack vector: remote (network-reachable)
Patched: 2.0.0 — apply immediately
Workaround: The only vulnerable code path is HTML output which is opt-in.
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.
Cross-site scripting (XSS) (CWE-79) exists in wlc.
Check the vendor advisory for the affected versions of wlc.
Severity: Medium (CVSS 5.1/10). Risk of unauthorized operations or information disclosure.
Update to 2.0.0.
Workaround: The only vulnerable code path is HTML output which is opt-in.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wlc' . 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
-
1Identify exposure identify
grep -r 'wlc' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wlcを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
The only vulnerable code path is HTML output which is opt-in.パッチが適用されるまでの応急処置として、The only vulnerable code path is HTML output which is opt-in. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade wlc to 2.0.0ステージング環境で 2.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-42150 wlc
- Ubuntu UBUNTU-CVE-2026-42150 wlc
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com