CVE-2022-21683
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account, but needs a user to act. Limited direct impact.
- Exploit odds
- 1.0% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.0% in the next 30 days (EPSS).
- Severity: 3.5 LOW (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.0% · EPSS, next 30 days
- Weakness
- CWE-200 · Information exposure
- Record status
- Modified
Affected
- Torchbox Wagtail < 2.15.2
Attack profile CVSS 3.1 · 3.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2022-21683.md and follow it. Check whether this project is affected by CVE-2022-21683. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/wagtail/wagtail/commit/5fe901e5d86ed02dbbb63039a897582951266afd
- https://github.com/wagtail/wagtail/releases/tag/v2.15.2
- https://github.com/wagtail/wagtail/security/advisories/GHSA-xqxm-2rpm-3889
- https://github.com/wagtail/wagtail/commit/5fe901e5d86ed02dbbb63039a897582951266afd
- https://github.com/wagtail/wagtail/releases/tag/v2.15.2
- https://github.com/wagtail/wagtail/security/advisories/GHSA-xqxm-2rpm-3889
References
- https://github.com/wagtail/wagtail/commit/5fe901e5d86ed02dbbb63039a897582951266afd
- https://github.com/wagtail/wagtail/releases/tag/v2.15.2
- https://github.com/wagtail/wagtail/security/advisories/GHSA-xqxm-2rpm-3889
- https://github.com/wagtail/wagtail/commit/5fe901e5d86ed02dbbb63039a897582951266afd
- https://github.com/wagtail/wagtail/releases/tag/v2.15.2
- https://github.com/wagtail/wagtail/security/advisories/GHSA-xqxm-2rpm-3889