CVE-2026-54262

CVE-2026-54262 is a medium-severity vulnerability in Torchbox Wagtail with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-280.

Key facts

Description

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, a low-level user with the "Can submit translation" permission can create translations for any page, including those they do not have permissions for. This issue has been fixed in versions 7.0.8, 7.3.3, and 7.4.2.

Frequently asked questions

What is CVE-2026-54262?
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, a low-level user with the "Can submit translation" permission can create translations for any page, including those they do not have permissions for. This issue has been fixed in versions 7.0.8, 7.3.3, and 7.4.2.
How severe is CVE-2026-54262?
CVE-2026-54262 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2026-54262 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-54262?
CVE-2026-54262 affects Torchbox Wagtail. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-54262?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-54262 published?
CVE-2026-54262 was published on 2026-07-01 and last updated on 2026-07-02.

References

Affected products (1)

More vulnerabilities in Torchbox Wagtail

All CVEs affecting Torchbox Wagtail →

Other CWE-280 vulnerabilities

Browse all CWE-280 vulnerabilities →