CVE-2022-21683: Comment reply notifications sent to incorrect users in wagtail
Impact 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 had editing access to, as long as they have left a comment or reply somewhere on the site.
Patches A patched version has been released as Wagtail 2.15.2 (for the current LTS), which restores the intended behaviour - to send notifications for new replies to the participants in the active thread only (editing permissions are not considered).
Workarounds New comments can be disabled by setting WAGTAILADMINCOMMENTSENABLED = False in the Django settings file.
Acknowledgements
Many thanks to Ihor Marhitych for identifying this issue.
For more information If you have any questions or comments about this advisory:
Visit Wagtail's support channels Email us at security@wagtail.io (if you wish to send encrypted email, the public key ID is 0x6ba1e1a86e0f8ce8)
Other sources
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 WAGTAILADMINCOMMENTSENABLED = False in the Django settings file.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the vulnerability ID for this issue in Wagtail?
The vulnerability ID for this issue in Wagtail is CVE-2022-21683.
What is the affected software version for Wagtail vulnerability CVE-2022-21683?
The affected software version for Wagtail vulnerability CVE-2022-21683 is versions 2.13 up to and including 2.15.2.
What is the severity of vulnerability CVE-2022-21683?
The severity of vulnerability CVE-2022-21683 is medium with a CVSS score of 4.3.
How can I fix vulnerability CVE-2022-21683 in Wagtail?
To fix vulnerability CVE-2022-21683 in Wagtail, update to version 2.15.3 or later.
Where can I find more information about vulnerability CVE-2022-21683 in Wagtail?
You can find more information about vulnerability CVE-2022-21683 in Wagtail at the following references: [GitHub Commit](https://github.com/wagtail/wagtail/commit/5fe901e5d86ed02dbbb63039a897582951266afd), [GitHub Release](https://github.com/wagtail/wagtail/releases/tag/v2.15.2), [GitHub Security Advisory](https://github.com/wagtail/wagtail/security/advisories/GHSA-xqxm-2rpm-3889).