SSRF (Server-Side Request Forgery) in Xibo (CVE-2026-42141)
Summary
SSRF in Xibo (CVE-2026-42141). Confidential information can be exposed externally. Mitigation: upgrade to 4.4.1 or later.
Original description
The description as published by the source.
Xibo is an open source digital signage platform with a web content management system and Windows display player software. Prior to 4.4.1, an authenticated Server-Side Request Forgery (SSRF) vulnerability in the Xibo CMS allows users with Library upload permissions to make arbitrary HTTP requests from the CMS server to internal or external network resources. This can be exploited to scan internal infrastructure, access local cloud metadata endpoints (e.g., AWS IMDS), interact with internal services that lack authentication, or exfiltrate data. This vulnerability is fixed in 4.4.1.
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-42141 has been found in Xibo.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade Xibo to 4.4.1 or later.
If unsure, ask your IT team or search "Xibo CVE-2026-42141" on the vendor's site.
CVE-2026-42141 (Xibo) — CWE-918 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.4.1 — 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.
SSRF (CWE-918) exists in Xibo.
Check the vendor advisory for the affected versions of Xibo.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 4.4.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Xibo' . 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 'Xibo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Xiboを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Xibo to 4.4.1ステージング環境で 4.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov