What is CVE-2024-53908?

CVE-2024-53908 is a high-severity SQL injection vulnerability in Django (pip), affecting versions >= 5.0.0, < 5.0.10. It is fixed in 5.0.10, 5.1.4, 4.2.17. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2024-53908?

CVE-2024-53908 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.

Which packages are affected by CVE-2024-53908?

Django (pip) versions >= 5.0.0, = 5.1, < 5.1.4.

Is there a fix for CVE-2024-53908?

Yes. CVE-2024-53908 is fixed in 5.0.10, 5.1.4, 4.2.17. Upgrade to this version or later.

Is CVE-2024-53908 exploitable, and should I be worried?

Whether CVE-2024-53908 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.

What actually determines whether CVE-2024-53908 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.

CVE-2024-53908 in Django | Intelligent Application Security

Q: How severe is CVE-2024-53908?

CVE-2024-53908 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.

Q: Which packages are affected by CVE-2024-53908?

Django (pip) versions >= 5.0.0, = 5.1, < 5.1.4.

Q: Is there a fix for CVE-2024-53908?

Yes. CVE-2024-53908 is fixed in 5.0.10, 5.1.4, 4.2.17. Upgrade to this version or later.

Q: Is CVE-2024-53908 exploitable, and should I be worried?

Whether CVE-2024-53908 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.

Q: What actually determines whether CVE-2024-53908 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.

Q: How do I fix CVE-2024-53908?

Upgrade: Django to 5.0.10 or later, Django to 5.1.4 or later, Django to 4.2.17 or later, django to 5.1.4 or later, django to 5.0.10 or later, django to 4.2.17 or later.

Summary

An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the django.db.models.fields.json.HasKey lookup, when an Oracle database is used, is subject to SQL injection if untrusted data is used as an lhs value. (Applications that use the jsonfield.has_key lookup via __ are unaffected.)

Impact

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-2024-53908 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 (5.0.10, 5.1.4, 4.2.17); upgrading removes the vulnerable code path.

Affected versions

Django (>= 5.0.0, < 5.0.10) Django (>= 5.1.0, < 5.1.4) Django (>= 4.2.0, < 4.2.17) django (>= 5.1, < 5.1.4) django (>= 5.0, < 5.0.10) django (>= 4.2, < 4.2.17)

Security releases

Django → 5.0.10 (pip) Django → 5.1.4 (pip) Django → 4.2.17 (pip) django → 5.1.4 (pip) django → 5.0.10 (pip) django → 4.2.17 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

Django to 5.0.10 or later; Django to 5.1.4 or later; Django to 4.2.17 or later; django to 5.1.4 or later; django to 5.0.10 or later; django to 4.2.17 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-53908? CVE-2024-53908 is a high-severity SQL injection vulnerability in Django (pip), affecting versions >= 5.0.0, < 5.0.10. It is fixed in 5.0.10, 5.1.4, 4.2.17. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is CVE-2024-53908? CVE-2024-53908 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.
Which packages are affected by CVE-2024-53908?
- Django (pip) (versions >= 5.0.0, < 5.0.10)
- django (pip) (versions >= 5.1, < 5.1.4)
Is there a fix for CVE-2024-53908? Yes. CVE-2024-53908 is fixed in 5.0.10, 5.1.4, 4.2.17. Upgrade to this version or later.
Is CVE-2024-53908 exploitable, and should I be worried? Whether CVE-2024-53908 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
What actually determines whether CVE-2024-53908 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.
How do I fix CVE-2024-53908?
- Upgrade Django to 5.0.10 or later
- Upgrade Django to 5.1.4 or later
- Upgrade Django to 4.2.17 or later
- Upgrade django to 5.1.4 or later
- Upgrade django to 5.0.10 or later
- Upgrade django to 4.2.17 or later

Other vulnerabilities in Django

CVE-2026-5766 CVE-2026-6907 CVE-2026-35192 CVE-2026-4277 CVE-2026-3902