# Django vulnerable to SQL injection in column aliases

Advisory record · `GHSA-hpr9-3m2g-3j9p`

- **Identifiers:** `GHSA-hpr9-3m2g-3j9p` · `BIT-django-2025-59681` · `CVE-2025-59681` · `PYSEC-2025-106`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 1 Oct 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Oct 2025, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `django` (PyPI): affected `>=4.2, <4.2.25 || >=5.1, <5.1.13 || >=5.2, <5.2.7`; fixed in `4.2.25`, `5.1.13`, `5.2.7`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Django versions 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7 are affected. On MySQL and MariaDB, an attacker who can supply a specially crafted dictionary that is expanded as keyword arguments to QuerySet.annotate(), alias(), aggregate(), or extra() can inject SQL through column aliases. Upgrade to Django 4.2.25, 5.1.13, or 5.2.7.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N`, from CNA (mitre)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0066, the 52nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:34 UTC: First seen by agentprime
- 31 Oct 2026, 14:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hpr9-3m2g-3j9p)

## Sources

- [GitHub Advisory Database: GHSA-hpr9-3m2g-3j9p](https://github.com/advisories/GHSA-hpr9-3m2g-3j9p)
- [OSV: GHSA-hpr9-3m2g-3j9p](https://osv.dev/vulnerability/GHSA-hpr9-3m2g-3j9p)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-59681>
- <https://github.com/django/django/commit/41b43c74bda19753c757036673ea9db74acf494a>
- <https://github.com/django/django/commit/43d84aef04a9e71164c21a74885996981857e66e>
- <https://docs.djangoproject.com/en/dev/releases/security>
- <https://github.com/django/django>
- <https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2025-106.yaml>
- <https://groups.google.com/g/django-announce>
- <https://www.djangoproject.com/weblog/2025/oct/01/security-releases>
- <http://www.openwall.com/lists/oss-security/2025/10/01/3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hpr9-3m2g-3j9p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hpr9-3m2g-3j9p/>. Everything for agents: <https://agentprime.io/llms.txt>.
