Skip to main content
No exploitation reportedFix available

CVE-2022-21683

No exploitation reported by the sources we read.

  • Published2022-01-18
  • Fixed in2.15.2
  • WeaknessCWE-200

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2022-01-1818:15CVE publishedNVD

Versions per branch

NVD · OSV
Torchbox wagtail
BranchAffectedFixed in
2.x≥ 2.13, < 2.15.22.15.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • wagtail
    Affected
    • = >= 2.13, < 2.15.2no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2022-01-18

Fix

  1. Update Torchbox wagtail to 2.15.2

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2025-04-23
  • CNACVSS 3.13.5known since 2026-10-23
  • NVDCVSS 3.14.3read 2026-10-23
  • NVDCVSS 2.04read 2026-10-23
  • CNAweakness (CWE)CWE-200known since 2026-10-23
  • NVDweakness (CWE)CWE-200read 2026-10-23
  • FIRST EPSSEPSS score1.0 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2022-01-18

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Published
2022-01-18
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-xqxm-2rpm-3889

Frequently asked questions

What is CVE-2022-21683?

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.

Is CVE-2022-21683 actively exploited?

Active exploitation of CVE-2022-21683 has not been confirmed. Its EPSS score was 1.0% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-21683?

CVE-2022-21683 has a CVSS v3 base score of 4.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.

Running wagtail? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record