Vulnerability in sqladmin (CVE-2026-54529)
Summary
Vulnerability in sqladmin (CVE-2026-54529). Risk of unauthorized operations or information disclosure. Exploitable via sortBy. Mitigation: upgrade to 0.27.1 or later.
Original description
The description as published by the source.
Summary
ModelView.sort_query() uses the attacker-controlled sortBy list-view query parameter without checking it against the configured column_sortable_list allow-list. The value is resolved with getattr(model, ...) and fed into relationship joins and order_by(), so a request can sort by any column of the model — including ones hidden from column_list — and, via a dotted path, by columns of related models. Because row order then reflects the value of an unexposed column, this is an information-exposure ordering oracle.
Root cause
column_sortable_list is consulted only in the list template to decide which header links to render; the server never enforces it, so removing a column from the UI does not prevent sorting by it.
Exploitation
A single request leaks the relative ordering of an unexposed column; the asc↔desc reversal confirms rows are ordered by the secret's actual value. Pairing sortBy with searchable/filterable columns and pagination can narrow the oracle toward specific values, though value recovery is conditional on having a filterable target column.
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-54529 has been found in sqladmin.
Attackers can target a specific entry point like sortBy over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade sqladmin to 0.27.1 or later.
If unsure, ask your IT team or search "sqladmin CVE-2026-54529" on the vendor's site.
CVE-2026-54529 (sqladmin) — CWE-20 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: sortBy / column_sortable_list / column_list / asc
Patched: 0.27.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.
A vulnerability (CWE-20) exists in sqladmin. Attackers reach the vulnerable code path via sortBy without authentication.
Check the vendor advisory for the affected versions of sqladmin. Attack surface: sortBy / column_sortable_list / column_list / asc.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.27.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 'sqladmin' . 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 'sqladmin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sqladminを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade sqladmin to 0.27.1ステージング環境で 0.27.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web security-advisories@github.com
- web github.com
- web github.com
- web github.com