Skip to content

Comment reply notifications sent to incorrect users

Low severity GitHub Reviewed Published Jan 18, 2022 in wagtail/wagtail • Updated Feb 3, 2023

Package

pip wagtail (pip)

Affected versions

>= 2.13, < 2.15.2

Patched versions

2.15.2

Description

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 WAGTAILADMIN_COMMENTS_ENABLED = 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:

References

@gasman gasman published to wagtail/wagtail Jan 18, 2022
Published by the National Vulnerability Database Jan 18, 2022
Reviewed Jan 18, 2022
Published to the GitHub Advisory Database Jan 21, 2022
Last updated Feb 3, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

EPSS score

0.070%
(32nd percentile)

Weaknesses

CVE ID

CVE-2022-21683

GHSA ID

GHSA-xqxm-2rpm-3889

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.