CVE-2021-30459

SQL Injection via in django-debug-toolbar

For more information

If you have any questions or comments about this advisory:

• Open an issue in the django-debug-toolbar repo (Please NO SENSITIVE INFORMATION, send an email instead!)
• Email us at [email protected]

With Django Debug Toolbar attackers are able to execute SQL by changing the raw_sql input of the SQL explain, analyze or select forms and submitting the form.

NOTE: This is a high severity issue for anyone using the toolbar in a production environment.

Generally the Django Debug Toolbar team only maintains the latest version of django-debug-toolbar, but an exception was made because of the high severity of this issue.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2021-30459 has a CVSS score of 9.8 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.11.1, 2.2.1, 3.2.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Please upgrade to one of the following versions, depending on the major version you're using:

• Version 1.x: django-debug-toolbar 1.11.1
• Version 2.x: django-debug-toolbar 2.2.1
• Version 3.x: django-debug-toolbar 3.2.1

1. What is CVE-2021-30459? CVE-2021-30459 is a high-severity SQL injection vulnerability in django-debug-toolbar (pip), affecting versions >= 0.10.0, < 1.11.1. It is fixed in 1.11.1, 2.2.1, 3.2.1. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2021-30459? CVE-2021-30459 has a CVSS score of 9.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of django-debug-toolbar are affected by CVE-2021-30459? django-debug-toolbar (pip) versions >= 0.10.0, < 1.11.1 is affected.
4. Is there a fix for CVE-2021-30459? Yes. CVE-2021-30459 is fixed in 1.11.1, 2.2.1, 3.2.1. Upgrade to this version or later.
5. Is CVE-2021-30459 exploitable, and should I be worried? Whether CVE-2021-30459 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2021-30459 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2021-30459?
   • Upgrade django-debug-toolbar to 1.11.1 or later
   • Upgrade django-debug-toolbar to 2.2.1 or later
   • Upgrade django-debug-toolbar to 3.2.1 or later