Wagtail: Improper restriction handling on Page translation API endpoint
- 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? →
- 22/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, has a flaw in its page translation API endpoint. A user with the submit translations permission can read the contents of a source page they are not allowed to edit, reached remotely over the network with low-privilege login and no user interaction.
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, a Wagtail CMS user with the submit translations permission can call the Admin API copy for translation action for a source page that the user cannot edit. The action copies the inaccessible page into a translation, allowing the user to view its contents despite the missing source-page edit permission. 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
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach12/20wagtail: 177.9K downloads a week
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
Impact
- Widely used
wagtail has 177.9k weekly downloads.Source: pypistats.org
410 packages depend on wagtail.Source: deps.dev
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
- wagtailPyPI
fixed in 7.0.9
Fixed in 7.0.9 (released Aug 20, 2026, 81 days before disclosure).
- wagtailPyPI
From 7.1rc1 · fixed in 7.3.4
Fixed in 7.3.4 (released Aug 20, 2026, 81 days before disclosure).
- wagtailPyPI
From 7.4rc1 · fixed in 7.4.3
Fixed in 7.4.3 (released Aug 20, 2026, 81 days before disclosure).
- wagtailPyPI
From 8.0rc1 · fixed in 8.0rc2
Fixed in 8.0.0rc2 (released Aug 20, 2026, 81 days before disclosure).
The latest release, 8.1.0, is not affected.
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-125106
Is CVE-2026-125106 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-125106?
wagtail: before 7.0.9; from 7.1 before 7.3.4; from 7.4 before 7.4.3. wagtail (PyPI): before 7.0.9. wagtail (PyPI): from 7.1rc1 before 7.3.4. wagtail (PyPI): from 7.4rc1 before 7.4.3. wagtail (PyPI): from 8.0rc1 before 8.0rc2.Source: cve.now feed data
How do I fix CVE-2026-125106?
Upgrade to a fixed version: 7.0.9, 7.3.4, 7.4.3.Source: cve.now feed data