Wagtail: Improper restriction handling on Documents and Images chosen endpoints
Wagtail is an open source content management system built on Django. In versions prior to 7.0.8, 7.3.3 and 7.4.2, the Documents and Images chooser's chosen endpoint incorrectly listed items for which the user has not been granted choose permission. A user with access to the Wagtail admin could see the filename and name and URLs of documents and images in those collections. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. This issue has been fixed in versions 7.0.8, 7.3.3, and 7.4.2.
- Published
- Jul 1, 2026
- Updated
- Jul 2, 2026
- EPSS
- 0.3% · 17th percentile
- CWE
- CWE-280
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 4.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| torchbox | wagtail | cpe:2.3:a:torchbox:wagtail |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- torchbox wagtailbefore 7.0.8
- torchbox wagtail7.1 and later · before 7.3.3
- torchbox wagtail7.4 and later · before 7.4.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
wagtail wagtail
- < 7.0.8, >= 7.1.0, < 7.3.3, >= 7.4.0, < 7.4.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | wagtail | from 7.1 · before 7.3.3 | 7.3.3 |
| PyPI | wagtail | from 7.4 · before 7.4.2 | 7.4.2 |
| PyPI | wagtail | before 7.0.8 | 7.0.8 |
Same product
torchbox: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-54263Wagtail: Reflected XSS in dynamic image URL generator view29Monitor
- CVE-2020-11001Possible XSS attack in Wagtail27Monitor
- CVE-2026-54261Wagtail: Improper permission handling in image preview26Monitor
- CVE-2026-44200Wagtail: Improper permission handling when copying pages26Monitor
- CVE-2026-44199Wagtail: Improper permission handling when deleting form submissions26Monitor
- CVE-2026-44197Wagtail: Improper permission handling when comparing revisions26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PyPI:wagtail | 7.0.8 | Package registry (OSV) |
| PyPI:wagtail | 7.3.3 | Package registry (OSV) |
| PyPI:wagtail | 7.4.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-542610 days apartWagtail: Improper permission handling in image preview26Monitor
- CVE-2026-4419751 days apartWagtail: Improper permission handling when comparing revisions26Monitor
- CVE-2026-4419951 days apartWagtail: Improper permission handling when deleting form submissions26Monitor
- CVE-2026-4420051 days apartWagtail: Improper permission handling when copying pages26Monitor
- CVE-2026-4420151 days apartWagtail: Improper restriction handling on Documents and Images API21Monitor
- CVE-2026-542620 days apartWagtail: Pages translations can be created without page permissions when using simple_translation17Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-280 · Improper Handling of Insufficient Permissions or PrivilegesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.