← Back
CVE-2025-64459
SQL Injection in django (CVE-2025-64459)
Summary
SQL injection in django (CVE-2025-64459). Confidential information can be exposed externally. Exploitable via ``_connector``. Mitigation: upgrade to `4.2.26, 5.1.14, 5.2.8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-64459** has been found in django.
Attackers can target a specific entry point like ``_connector`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade django to **4.2.26, 5.1.14, 5.2.8** or later.
If unsure, ask your IT team or search "django CVE-2025-64459" on the vendor's site.
CVE-2025-64459 (django) — CWE-89 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `_connector`
Patched: `4.2.26, 5.1.14, 5.2.8` — 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.
❓ What is the problem
**SQL injection** (CWE-89) exists in django. Attackers reach the vulnerable code path via ``_connector`` without authentication.
📍 Affected scope
django — . Attack surface: `_connector`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **4.2.26, 5.1.14, 5.2.8**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'django' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'django' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `django` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade django to 4.2.26, 5.1.14, 5.2.8ステージング環境で 4.2.26, 5.1.14, 5.2.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
django
[{"type":"SEMVER","events":[{"introduced":"4.2.0"},{"fixed":"4.2.26"},{"introduced":"5.1.0"},{"fixed":"5.1.14"},{"introduced":"5.2.0"},{"fixed":"5.2.8"}]}]
PyPI
django
[{"type":"ECOSYSTEM","events":[{"introduced":"4.2"},{"fixed":"4.2.26"},{"introduced":"5.1"},{"fixed":"5.1.14"},{"introduced":"5.2"},{"fixed":"5.2.8"}]}]
pip
django
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.26"}]}]
References
- advisory https://docs.djangoproject.com/en/dev/releases/security/
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-64459
- advisory https://www.djangoproject.com/weblog/2025/nov/05/security-releases/
- advisory https://github.com/advisories/GHSA-frmv-pr5f-9mcr
- package https://github.com/django/django
- report https://shivasurya.me/security/django/2025/11/07/django-sql-injection-CVE-2025-64459.html
- web https://groups.google.com/g/django-announce
- web https://github.com/django/django/commit/06dd38324ac3d60d83d9f3adabf0dcdf423d2a85
- web https://github.com/django/django/commit/59ae82e67053d281ff4562a24bbba21299f0a7d4
- web https://github.com/django/django/commit/6703f364d767e949c5b0e4016433ef75063b4f9b
- web https://github.com/django/django/commit/72d2c87431f2ae0431d65d0ec792047f078c8241
- web https://docs.djangoproject.com/en/dev/releases/security
- web https://github.com/omarkurt/django-connector-CVE-2025-64459-testbed
- web https://www.djangoproject.com/weblog/2025/nov/05/security-releases
- web https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2025-108.yaml