Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

SQLAdmin: Unvalidated sortBy parameter in ModelView bypasses column_sortable_list

CVE-2026-54529GHSA-ccg5-9c8w-xh6v

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (sqladmin 0.27.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI sqladmin

    Affected
    < 0.27.1
    Fixed in
    0.27.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-54529: 0.38% estimated exploitation activity in the next 30 days; percentile 32.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary ModelView.sortquery() uses the attacker-controlled sortBy list-view query parameter without checking it against the configured columnsortablelist allow-list. The value is resolved with getattr(model, ...) and fed into relationship joins and orderby(), so a request can sort by any column of the model — including ones hidden from columnlist — 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 columnsortablelist 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,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-ccg5-9c8w-xh6v

  2. Revision 2 · amended ·

    Amended from osv record GHSA-ccg5-9c8w-xh6v

  3. Revision 1 · created ·

    Published from ghsa record GHSA-ccg5-9c8w-xh6v

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54529

Advisory: SQLAdmin: Unvalidated sortBy parameter in `ModelView` bypasses `column_sortable_list`
IDs: CVE-2026-54529, GHSA-ccg5-9c8w-xh6v
Record: https://patchnext.com/advisories/cve-2026-54529 (revision 3, source checked 26 Oct 2026, 13:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sqladmin 0.27.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI sqladmin: affected < 0.27.1; fixed in 0.27.1

## Suggested inspection (read-only)
- `python -m pip show sqladmin`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sqladmin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ccg5-9c8w-xh6v (GitHub-reviewed advisory GHSA-ccg5-9c8w-xh6v lists affected ranges: PyPI sqladmin >=0 <0.27.1)
- Verified: https://osv.dev/vulnerability/GHSA-ccg5-9c8w-xh6v (OSV record GHSA-ccg5-9c8w-xh6v lists affected ranges: PyPI sqladmin >=0 <0.27.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…