CVE-2026-123819: Wagtail: Improper permission handling when copying snippets
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- 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.
- Fixed version: wagtail (PyPI) 7.3.4, 7.4.3, 8.0rc2.
Low priority for now. Upgrade to wagtail (PyPI) 7.3.4, 7.4.3, 8.0rc2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 CMS user who has add permission for a snippet model but lacks change and view permission for an existing snippet can access the snippet copy view and copy that source object. The copy operation reveals the contents of a snippet that the user is not authorized to view. This issue is fixed in versions 7.0.9, 7.3.4, 7.4.3, and 8.0rc2.
- Published
- Nov 9, 2026
- Updated
- Nov 13, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- CWE-280
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 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
- 6.5
- 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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
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.9, >= 7.1, < 7.3.4, >= 7.4, < 7.4.3, = 8.0rc1affected
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.4 | 7.3.4 |
| PyPI | wagtail | from 7.4 · before 7.4.3 | 7.4.3 |
| PyPI | wagtail | from 8.0rc1 · before 8.0rc2 | 8.0rc2 |
| PyPI | wagtail | before 7.0.9 | 7.0.9 |
Same product
wagtail: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-125106Wagtail: Improper restriction handling on Page translation API endpoint26Monitor
- CVE-2024-35228Improper Handling of Insufficient Permissions in Wagtail22Monitor
- CVE-2026-123820Wagtail: Improper restriction handling on descendant collections in Documents and Images API21Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-32882May 2, 2024 · Permission check bypass when editing a model with per-field restrictions in wagtail10Monitor
- ← EarlierCVE-2026-55468Aug 24, 2026 · Wagtail: Improper restriction handling on Pages admin API17Monitor
- Later →CVE-2026-125105Nov 9, 2026 · Wagtail: Identification of documents by SHA1 hash14Monitor
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.9 | Package registry (OSV) |
| PyPI:wagtail | 7.3.4 | Package registry (OSV) |
| PyPI:wagtail | 7.4.3 | Package registry (OSV) |
| PyPI:wagtail | 8.0rc2 | 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.
- Published
- Fix recordedsame day
- TodayNov 16, 2026+7 d
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1251060 days apartWagtail: Improper restriction handling on Page translation API endpoint26Monitor
- CVE-2026-1238200 days apartWagtail: Improper restriction handling on descendant collections in Documents and Images API21Monitor
- CVE-2026-5546877 days apartWagtail: Improper restriction handling on Pages admin API17Monitor
- CVE-2026-1251050 days apartWagtail: Identification of documents by SHA1 hash14Monitor
Not on record for this CVE: researcher credit · public bounty program.
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
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- 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:H/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.
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/wagtail/wagtail/commit/5afd40f0bc04f7986256ced8ec959af30e1446be
- github.com/wagtail/wagtail/commit/aebf89233c0cc9739e240e1112d705e0c995f79c
- github.com/wagtail/wagtail/commit/c06183cc9c9590e4585f27899173bc741bbbcb10
- github.com/wagtail/wagtail/releases/tag/v7.0.9
- github.com/wagtail/wagtail/releases/tag/v7.3.4
- github.com/wagtail/wagtail/releases/tag/v7.4.3
- github.com/wagtail/wagtail/releases/tag/v8.0rc2
- github.com/wagtail/wagtail/security/advisories/GHSA-x5cx-w6p2-mxf2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.