Approved changes feed: RSS · Atom

cpe:2.3:a:torchbox:wagtail:*:*:*:*:lts:*:*:*

part: a version: * update: *

VendorTorchbox (666bfbcf-6d5f-53ec-9227-cd1490758256)
ProductWagtail (f36a103b-15d1-5403-9536-f9aecfc6315c)
Edition*
Language*
Software editionlts
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/wagtail/wagtail purl2cpe 2026-06-01 10:16:49.324680
pkg:pypi/wagtail purl2cpe 2026-06-01 10:16:49.324682
pkg:rpm/opensuse/python-wagtail purl2cpe 2026-06-01 10:16:49.324683
pkg:sourceforge/wagtail.mirror purl2cpe 2026-06-01 10:16:49.324685

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2021-29434 vulnerable 2026-06-08 05:31:26.350083 Improper validation of URLs ('Cross-site Scripting') in Wagtail rich text fields
MEDIUM (6.1)
Wagtail is a Django content management system. In affected versions of Wagtail, when saving the contents of a rich text field in the admin interface, Wagtail does not apply server-side checks to ensure that link URLs use a valid protocol. A malicious user with access to the admin interface could thus craft a POST request to publish content with `javascript:` URLs containing arbitrary code. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. See referenced GitHub advisory for additional details, including a workaround. Patched versions have been released as Wagtail 2.11.7 (for the LTS 2.11 branch) and Wagtail 2.12.4 (for the current 2.12 branch).
Published: 2021-04-19T18:45:14.000Z
Updated: 2024-08-03T22:02:51.911Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2020-11037 vulnerable 2026-06-08 05:16:36.345803 Potential Observable Timing Discrepancy in Wagtail
MEDIUM (6.1)
In Wagtail before versions 2.7.3 and 2.8.2, a potential timing attack exists on pages or documents that have been protected with a shared password through Wagtail's "Privacy" controls. This password check is performed through a character-by-character string comparison, and so an attacker who is able to measure the time taken by this check to a high degree of accuracy could potentially use timing differences to gain knowledge of the password. This is [understood to be feasible on a local network, but not on the public internet](https://groups.google.com/d/msg/django-developers/iAaq0pvHXuA/fpUuwjK3i2wJ). Privacy settings that restrict access to pages/documents on a per-user or per-group basis (as opposed to a shared password) are unaffected by this vulnerability. This has been patched in 2.7.3, 2.8.2, 2.9.
Published: 2020-04-30T22:20:12.000Z
Updated: 2024-11-19T15:42:15.578Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.