CVE-2024-3572
XML External Entity (XXE) Vulnerability in scrapy/scrapy
CVE-2024-3572 affects Scrapy Scrapy/scrapy (CVSS 7.5, High).
Public exploit available. Not confirmed exploited in the wild yet. Fixed in 2.11.1.
Public exploit: 1 sourceFix2.11.1Upgrade to this build
e.g. OID 1.3.6.1.4.1.25623.1.1.12.2025.7476.1
What to do
Find your product and version, then upgrade to the build on the right.
- Scrapy/scrapyAffected: ≥ unspecified, < 2.11.1Upgrade to: 2.11.1Stated by: CVE record
- PyPI scrapyAffected: ≥ 2.0.0, < 2.11.1Upgrade to: 2.11.1Stated by: GitHub advisory
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
The scrapy/scrapy project is vulnerable to XML External Entity (XXE) attacks due to the use of lxml.etree.fromstring for parsing untrusted XML data without proper validation. This vulnerability allows attackers to perform denial of service attacks, access local files, generate network connections, or circumvent firewalls by submitting specially crafted XML data.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
1 source with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
0.8% chance of exploitation activity in the next 30 days, which ranks it in the 58th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
The patch came 221 days before any public exploit.
- OpenVAS check added
- Public exploit / PoCsource: other
- Patch availablerecord updated
- Publishedweakness classified
Affected products
Technical detail
CVSS 3.0 vector
Open in the CVSS calculatorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Scored 7.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
Sources
Questions about CVE-2024-3572
- Is CVE-2024-3572 being exploited?
- Not confirmed. Public exploit code exists (1 source), but CVE-2024-3572 is not in CISA KEV. EPSS puts the chance of exploitation in the next 30 days at 0.8%.
- Which versions are affected by CVE-2024-3572?
- Scrapy/scrapy: ≥ unspecified, < 2.11.1. Scrapy: ≥ 2.0.0, < 2.11.1.
- How do I fix or mitigate CVE-2024-3572?
- Upgrade to 2.11.1 or later. The advisory is on github.com.
Last updated
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Scrapy/scrapy, not every advisory. This one: public exploit.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI