Cross-Site Scripting (XSS) in backpack/crud (CVE-2026-54181)
Summary
Cross-site scripting in backpack/crud (CVE-2026-54181). Risk of unauthorized operations or information disclosure. Exploitable via color. Mitigation: upgrade to 7.0.38 or later.
Original description
The description as published by the source.
Summary
The Blade template for the color column type (src/resources/views/crud/columns/color.blade.php) has its escaped/unescaped rendering branches inverted relative to every other column template in the library. Because $column['escaped'] defaults to true, values stored in color columns are rendered unescaped by default, enabling Stored XSS if column values are not validated before storage.
Details
All other column templates in src/resources/views/crud/columns/ follow the convention:
$column['escaped'] == true→{{ $column['text'] }}(HTML-escaped)$column['escaped'] == false→{!! $column['text'] !!}(raw)
The color template has these branches swapped. An attacker who can write an arbitrary string to a color-typed column can inject JavaScript that executes in the browser of any user who views the list — including administrators — with access to their session cookies and CSRF tokens.
Impact
Stored XSS with scope change (attacker context runs in victim's browser). Highest-risk target is an administrator viewing the list view. Exploitability requires the ability to write an unsanitized value into a color-typed column.
Patches
Fixed in 6.8.14 and 7.0.38 by correcting the branch order in color.blade.php. See PR #5992.
Workarounds
Validate stored color values against a strict CSS color grammar (e.g. /^#[0-9a-fA-F]{3,6}$/) at the model layer before data reaches the view.
Credits
Reported by Vishal Shukla ([…
Source: GitHub Security Advisories (Global) 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-54181 has been found in backpack/crud.
Attackers can target a specific entry point like color over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade backpack/crud to 7.0.38 or later.
If unsure, ask your IT team or search "backpack/crud CVE-2026-54181" on the vendor's site.
CVE-2026-54181 (backpack/crud) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Attack surface: color / true / color.blade.php
Patched: 7.0.38 — apply immediately
Workaround: Validate stored color values against a strict CSS color grammar (e.g.
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 backpack/crud. Attackers reach the vulnerable code path via color.
Check the vendor advisory for the affected versions of backpack/crud. Attack surface: color / true / color.blade.php.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 7.0.38.
Workaround: Validate stored color values against a strict CSS color grammar (e.g.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'backpack/crud' . 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 'backpack/crud' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
backpack/crudを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Validate stored color values against a strict CSS color grammar (e.g.パッチが適用されるまでの応急処置として、Validate stored color values against a strict CSS color grammar (e.g. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade backpack/crud to 7.0.38ステージング環境で 7.0.38 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com