Wagtail: Identification of documents by SHA1 hash
- Exploited
- No known exploitation
- Fix
- Fixed in 7.0.9, 7.3.4, 7.4.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.0.9, 7.3.4, 7.4.3.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Wagtail, an open source content management system built on Django, can leak whether a given SHA1 hash matches a document in its library. An attacker can reach this remotely without logging in, but only if they already know the document ID and the candidate hash.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Wagtail is an open source content management system built on Django. Prior to 7.0.9, 7.3.4, 7.4.3, and 8.0rc2, Wagtail applies ETag conditional request processing to the document serve endpoint before document permission and filename checks complete. An unauthenticated attacker who knows a document ID and a candidate SHA1 hash can submit If-Match or If-None-Match and distinguish the response, revealing whether that hash is present in the document library. The issue does not expose document contents, filenames, other metadata, or information about hashes the attacker does not already know. This issue is fixed in versions 7.0.9, 7.3.4, 7.4.3, and 8.0rc2.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity3.7/10CVSS 3.7
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 7.0.9, 7.3.4, 7.4.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wagtail wagtail
fixed in 7.0.9; From 7.1 · fixed in 7.3.4; From 7.4 · fixed in 7.4.3
Evidence 9
- Advisory
- Repository
- Repository
- Repository
- Repository
Show all 9 sourcesShow fewer sources
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125105
Is CVE-2026-125105 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-125105?
wagtail: before 7.0.9; from 7.1 before 7.3.4; from 7.4 before 7.4.3.Source: cve.now feed data
How do I fix CVE-2026-125105?
Upgrade to a fixed version: 7.0.9, 7.3.4, 7.4.3.Source: cve.now feed data