Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-44200: Wagtail: Improper permission handling when copying pages

MediumCVSS 6.5 · v3.1—No exploit Fix available

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.20% (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 wagtail 7.0.7.

Low priority for now. Upgrade to wagtail wagtail 7.0.7 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.7, 7.3.2, and 7.4, a CMS user with limited access to pages could copy a page they don't have access to to an area of the site they do. Once coped, they'd be able to view its contents, and potentially publish it. Permissions were correctly checked for the copy destination, but not for the source page. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.

Published
May 11, 2026
Updated
Nov 11, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2026-44200

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for torchbox records
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
torchboxwagtail

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.7, >= 7.1, < 7.3.2affected

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.7
  • torchbox wagtail7.1 and later · before 7.3.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPIwagtailfrom 7.1 · before 7.3.27.3.2
PyPIwagtailbefore 7.0.77.0.7

Same product

torchbox: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-54263Wagtail: Reflected XSS in dynamic image URL generator view
    29Monitor
  • CVE-2020-11001Possible XSS attack in Wagtail
    27Monitor
  • CVE-2026-54261Wagtail: Improper permission handling in image preview
    26Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-44198May 11, 2026 · Wagtail: Improper permission handling when viewing page history
    17Monitor
  • ← EarlierCVE-2026-44199May 11, 2026 · Wagtail: Improper permission handling when deleting form submissions
    26Monitor
  • Later →CVE-2026-44201May 11, 2026 · Wagtail: Improper restriction handling on Documents and Images API
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
wagtail wagtail7.0.7 · descriptionVendor (CNA)
PyPI:wagtail7.0.7Package registry (OSV)
PyPI:wagtail7.3.2Package 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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-441970 days apartWagtail: Improper permission handling when comparing revisions
    26Monitor
  • CVE-2026-441990 days apartWagtail: Improper permission handling when deleting form submissions
    26Monitor
  • CVE-2026-5426151 days apartWagtail: Improper permission handling in image preview
    26Monitor
  • CVE-2026-442010 days apartWagtail: Improper restriction handling on Documents and Images API
    21Monitor
  • CVE-2026-441980 days apartWagtail: Improper permission handling when viewing page history
    17Monitor
  • CVE-2026-5425951 days apartWagtail: Improper restriction handling on Documents and Images chosen endpoints
    17Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · 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 Privileges

CVSS 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.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records