vciy

CVE-2024-39614

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14

CVE-2024-396143 of 4 sources documented this
24

rank 24 = 19 + 0 + 1 + 4 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.28637  ·  without this subject the record ranks 5

What it costs you if it fires

NVD CVSS base score, then the CNA's own

no CVSS held by anyone  ·  without this subject the record ranks 24

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-09-16  ·  without this subject the record ranks 23

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 20

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 24

Hindsight · the state

0.28637EPSSNOT IN KEVas of 2026-09-20
Severitynot scored
Harmnot stated
Exploitationpublic proof-of-conceptreceipt
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
RISING10Risen from 0.00045 to 0.28637 across 63 observations. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Check a version against this record

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classCWE-130 Improper Handling of Length Parameter Inconsistencyreceipt
Published consequencesCWE-130: Confidentiality, Integrity: Read Memory, Modify Memory, Varies by Context[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchdjango 4.2.14; django 5.0.7receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2024-08-02.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2024-08-02receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.28637 · top 2% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes66 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesDjangoproject djangoreceipt
Published rangesdjangoproject django >= 4.2 < 4.2.14; djangoproject django >= 5.0 < 5.0.7receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. get_supported_language_variant() was subject to a potential denial-of-service attack when used with very long strings containing specific characters. receipt

NVD's analysis a second authority

weakness
CWE-130
affected versions
djangoproject django >= 4.2 < 4.2.14; djangoproject django >= 5.0 < 5.0.7
also scored by
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

check it yourself docs.djangoproject.com groups.google.com djangoproject.com receipt

Dated events

2025-03-17EPSS moved 0.00 to 0.622026-06-15EPSS moved 0.07 to 0.30

Movement the material steps

10 Jul 20240.00045
17 Mar 20250.61574 · crossed 0.10 and 0.50 · scoring model v2025.03.14
18 Mar 20250.39095 · crossed 0.50
19 Mar 20250.61574 · crossed 0.50
20 Mar 20250.13337 · crossed 0.50
23 Mar 20250.61574 · crossed 0.50
27 Mar 20250.75146
28 Mar 20250.17543 · crossed 0.50
29 Mar 20250.6755 · crossed 0.50
30 Mar 20250.17543 · crossed 0.50
15 Apr 20250.05412 · crossed 0.10
18 Nov 20250.21877 · crossed 0.10
21 Nov 20250.06838 · crossed 0.10
15 Jun 20260.30129 · crossed 0.10 · scoring model v2026.06.15
27 Jun 20260.28637

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 63 observations
10 Jul 20240.00045
17 Mar 20250.61574
18 Mar 20250.39095
19 Mar 20250.61574
20 Mar 20250.13337
23 Mar 20250.61574
26 Mar 20250.6755
27 Mar 20250.75146
28 Mar 20250.17543
29 Mar 20250.6755
30 Mar 20250.17543
5 Apr 20250.10061
7 Apr 20250.21711
13 Apr 20250.10061
14 Apr 20250.21711
15 Apr 20250.05412
17 Apr 20250.02585
18 Apr 20250.05412
19 Apr 20250.02585
20 Apr 20250.05412
26 Apr 20250.05833
1 May 20250.02794
6 May 20250.03264
11 May 20250.06765
1 Jun 20250.03264
5 Jun 20250.06765
17 Jun 20250.02989
1 Jul 20250.01449
5 Jul 20250.02989
1 Aug 20250.01449
5 Aug 20250.02989
11 Aug 20250.0276
17 Aug 20250.02375
1 Sep 20250.02123
4 Sep 20250.02375
16 Sep 20250.05866
17 Sep 20250.05718
19 Sep 20250.05866
1 Oct 20250.0527
2 Oct 20250.05136
4 Oct 20250.05718
21 Oct 20250.06838
1 Nov 20250.06151
4 Nov 20250.06838
18 Nov 20250.21877
21 Nov 20250.06838
1 Dec 20250.06151
4 Dec 20250.06838
1 Jan 20260.06151
4 Jan 20260.06838
18 Jan 20260.07012
26 Jan 20260.06838
1 Feb 20260.06151
4 Feb 20260.06838
5 Feb 20260.07012
14 Feb 20260.05866
19 Feb 20260.05718
23 Feb 20260.05866
1 Mar 20260.06309
4 Mar 20260.07012
9 Mar 20260.06838
15 Jun 20260.30129
27 Jun 20260.28637

63 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.28637Published2024-07-10Public PoC2024-08-02Index as of2026-06-27

Exploit probability more than doubled between 2025-03-20 and 2025-03-23 (0.13337 → 0.61574) and the record had been public for 1 year, 11 months when this index was last written.

Published 2024-07-10 receipt · Public PoC 2024-08-02 receipt · Index as of 2026-06-27 derived

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

Of the 4 records in this advisory that state one, this holds the highest EPSS percentile: 0.98002.

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

These are index-wide views, not findings about CVE-2024-39614.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.