cve.bz

CVE-2024-39317 torchbox wagtail

4.9 mediumEPSS 0.6%Fix available

Medium (4.9) in torchbox wagtail. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in wagtail 5.2.6, 6.0.6, 6.1.3.

On this page
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.

Severity

CVSS 3.1

4.9 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-07-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1333 Inefficient Regular Expression Complexity
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-39317 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-39317?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-39317?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-39317 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
torchbox:wagtailfrom 2.0 before 5.2.6
torchbox:wagtailfrom 6.0 before 6.0.6
torchbox:wagtailfrom 6.1 before 6.1.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jmp3-39vp-fwg8PyPIwagtail>=6.0 <6.0.66.0.6
GHSA-jmp3-39vp-fwg8PyPIwagtail>=6.1 <6.1.36.1.3
GHSA-jmp3-39vp-fwg8PyPIwagtail>=2.0 <5.2.65.2.6
PYSEC-2024-86PyPIwagtail>=6.0 <6.0.6
>=6.1 <6.1.3
>=2.0 <5.2.6
6.0.6, 6.1.3, 5.2.6

Attack patterns (CAPEC)

  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON