Skip to main content
No exploitation reportedFix available

CVE-2024-39317

No exploitation reported by the sources we read.

  • Published2024-07-11
  • Fixed in6.1.3 · 6.0.6 · 5.2.6
  • WeaknessCWE-1333

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Wagtail is an open source content management system built on Django. A bug in Wagtail's `parse_query_string` would result in it taking a long time to process suitably crafted inputs. When used to parse sufficiently long strings of characters without a space, `parse_query_string` would take an unexpectedly large amount of time to process, resulting in a denial of service. In an initial Wagtail installation, the vulnerability can be exploited by any Wagtail admin user. It cannot be exploited by end users. If your Wagtail site has a custom search implementation which uses `parse_query_string`, it may be exploitable by other users (e.g. unauthenticated users). Patched versions have been released as Wagtail 5.2.6, 6.0.6 and 6.1.3.

Timeline

dates in UTC
  1. 2024-07-1116:15CVE publishedNVD

Versions per branch

NVD · OSV
Torchbox wagtail
BranchAffectedFixed in
6.1≥ 6.1, < 6.1.36.1.3
6.0≥ 6.0, < 6.0.66.0.6
5.2≥ 2.0, < 5.2.65.2.6

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • wagtail
    Affected
    • = >= 2.0, < 5.2.6no fix stated
    • = >= 6.0, < 6.0.6no fix stated
    • = >= 6.1, < 6.1.3no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-07-11

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • rootio-wagtailRoot:PyPIall versions · fixed in 4.2.3+root.io.1

Full record on NVD

Fix

  1. Update Torchbox wagtail to 6.1.3 · 6.0.6 · 5.2.6

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2024-07-17
  • CNACVSS 3.16.5known since 2026-10-23
  • NVDCVSS 3.14.9read 2026-10-23
  • CNAweakness (CWE)CWE-1333known since 2026-10-23
  • NVDweakness (CWE)CWE-1333read 2026-10-23
  • FIRST EPSSEPSS score0.6 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2024-07-11

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
Published
2024-07-11
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-jmp3-39vp-fwg8

Frequently asked questions

What is CVE-2024-39317?

Wagtail is an open source content management system built on Django. A bug in Wagtail's `parse_query_string` would result in it taking a long time to process suitably crafted inputs. When used to parse sufficiently long strings of characters without a space, `parse_query_string` would take an unexpectedly large amount of time to process, resulting in a denial of service. In an initial Wagtail installation, the vulnerability can be exploited by any Wagtail admin user. It cannot be exploited by end users. If your Wagtail site has a custom search implementation which uses `parse_query_string`, it may be exploitable by other users (e.g. unauthenticated users). Patched versions have been released as Wagtail 5.2.6, 6.0.6 and 6.1.3.

Is CVE-2024-39317 actively exploited?

Active exploitation of CVE-2024-39317 has not been confirmed. Its EPSS score was 0.6% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-39317?

CVE-2024-39317 has a CVSS v3 base score of 4.9 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H.

Running wagtail? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record