CVE-2024-53908: Djangoproject vulnerability
Djangoproject · Django
Affected: Djangoproject · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 73% of scored CVEs
DescriptionCVE.org
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.)
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- SQL Injection
- Vendor
- Djangoproject
- Published
- December 2024
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2024-53908
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- CVE-2024-53908: Django Potential SQL injection in `HasKey(lhs, rhs)` on OracleInternet Bug Bounty · 2025 · high severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2024-53908 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.