Is CVE-2026-44199 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44199 being exploited in the wild.

How severe is CVE-2026-44199?

Medium severity, with a CVSS score of 6.5, published 11 May 2026.

Which products and versions are affected?

wagtail (PyPI) ECOSYSTEM:introduced=0,fixed=7.0.7, ECOSYSTEM:introduced=0,fixed=7.0.7,introduced=7.1,fixed=7.3.2; Wagtail = 7.1, < 7.3.2, < 7.0.7, 7.1 - 7.3.1.

Is there a fix for CVE-2026-44199?

Yes. wagtail (PyPI): upgrade to 7.0.7, 7.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44199 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44199?

Check whether you run wagtail (PyPI) or Wagtail at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44199: Wagtail improper permission handling in form submission deletion

Q: Is there a fix for CVE-2026-44199?

Yes. wagtail (PyPI): upgrade to 7.0.7, 7.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-44199 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-44199?

Check whether you run wagtail (PyPI) or Wagtail at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44199 · Severity: medium · CVSS 6.5 · Published 2026-05-11

Wagtail, a popular open-source content management system (CMS), contains a flaw in how it handles permissions for form submissions. An internal user with limited access can delete form data from pages they are not authorized to manage by manipulating web requests. This could lead to the unauthorized loss of customer-submitted data and disrupt business operations that rely on those forms.

Technologies: wagtail (PyPI), Wagtail. Vendors: PyPI, Wagtail.

Quick answers

Is CVE-2026-44199 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44199 being exploited in the wild.
How severe is CVE-2026-44199?: Medium severity, with a CVSS score of 6.5, published 11 May 2026.
Which products and versions are affected?: wagtail (PyPI) ECOSYSTEM:introduced=0,fixed=7.0.7, ECOSYSTEM:introduced=0,fixed=7.0.7,introduced=7.1,fixed=7.3.2; Wagtail < 7.0.7, >= 7.1, < 7.3.2, < 7.0.7, 7.1 - 7.3.1.
Is there a fix for CVE-2026-44199?: Yes. wagtail (PyPI): upgrade to 7.0.7, 7.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44199 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44199?: Check whether you run wagtail (PyPI) or Wagtail at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

wagtail (PyPI): upgrade to 7.0.7, 7.3.2 or later
```
pip install "wagtail>=7.3.2"
```

Technical details

Wagtail is vulnerable to improper handling of insufficient permissions (CWE-280) within its form submission management component. A CMS user with restricted access can bypass intended authorization checks by crafting a malicious form submission request. This allows the attacker to delete form submissions associated with pages they are not permitted to manage. The attack requires the attacker to have at least low-level 'limited access' privileges within the Wagtail admin interface. The issue is resolved in versions 7.0.7, 7.3.2, and 7.4 LTS.

Affected products

Wagtail Wagtail < 7.0.7, >= 7.1, < 7.3.2

Identifiers

CVE-2026-44199
GHSA-pwm3-7fv4-g6xx
PYSEC-2026-148

Timeline

2026-05-05: patched: Patched versions 7.0.7 and 7.3.2 released.
2026-05-08: disclosed: GitHub Advisory published.
2026-05-11: advisory: NVD published CVE-2026-44199.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.