VDB

CVE-2019-7164

CVE-2019-7164 PUBLISHED CVSS 9.800000190734863 CRITICAL

SQLAlchemy vulnerable to SQL Injection via order_by parameter

Reported by mitre · Published February 20, 2019

sqlalchemy is fixed in 1.3.0b3, 1.3.0 and 1.2.18 (PyPI)

SQLAlchemy through 1.2.17 and 1.3.x through 1.3.0b2 allows SQL Injection via the order_by parameter.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
sqlalchemyPyPI1.3.0b3, 1.3.0, 1.2.18
sqlalchemysqlalchemy1.2.17

Risk scores

CVSS 3.1
9.800000190734863
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

VendorProductVersions
n/an/an/a
n/an/a*
PyPIsqlalchemy0

Timeline

  • Feb 20, 2019 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Mar 9, 2026 Security Advisory (9 in total, the first dated here)
  • Sep 8, 2026 Coalition ESS Score
  • Sep 20, 2026 CVE Updated
  • Oct 31, 2026 Distribution Patch (2 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2019-7164
vulnetix vdb fixes CVE-2019-7164

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2019-7164/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›