CVE-2022-21683
Description
Wagtail is a Django based content management system focused on flexibility and user experience. When notifications for new replies in comment threads are sent, they are sent to all users who have replied or commented anywhere on the site, rather than only in the relevant threads. This means that a user could listen in to new comment replies on pages they have not have editing access to, as long as they have left a comment or reply somewhere on the site. A patched version has been released as Wagtail 2.15.2, which restores the intended behaviour - to send notifications for new replies to the participants in the active thread only (editing permissions are not considered). New comments can be disabled by setting `WAGTAILADMIN_COMMENTS_ENABLED = False` in the Django settings file.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://github.com/wagtail/wagtail/security/advisories/GHSA-xqxm-2rpm-3889
- https://nvd.nist.gov/vuln/detail/CVE-2022-21683
- https://github.com/wagtail/wagtail/commit/5fe901e5d86ed02dbbb63039a897582951266afd
- https://github.com/pypa/advisory-database/tree/main/vulns/wagtail/PYSEC-2022-13.yaml
- https://github.com/wagtail/wagtail
- https://github.com/wagtail/wagtail/releases/tag/v2.15.2
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.