cve.bz

CVE-2020-11037 torchbox wagtail: Race Condition

4.7 mediumEPSS 0.2%Fix available

Medium (4.7) in torchbox wagtail. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in wagtail 2.7.3, 2.8.2, 2.9.

On this page
In Wagtail before versions 2.7.3 and 2.8.2, a potential timing attack exists on pages or documents that have been protected with a shared password through Wagtail's "Privacy" controls. This password check is performed through a character-by-character string comparison, and so an attacker who is able to measure the time taken by this check to a high degree of accuracy could potentially use timing differences to gain knowledge of the password. This is [understood to be feasible on a local network, but not on the public internet](https://groups.google.com/d/msg/django-developers/iAaq0pvHXuA/fpUuwjK3i2wJ). Privacy settings that restrict access to pages/documents on a per-user or per-group basis (as opposed to a shared password) are unaffected by this vulnerability. This has been patched in 2.7.3, 2.8.2, 2.9.

Severity

CVSS 3.1

4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
CWE-208 Observable Timing Discrepancy
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • wagtail (PyPI): fixed in 2.7.3, 2.8.2, 2.9

Ask an AI about this CVE

Show the promptExplain CVE-2020-11037 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-11037?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-11037?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-11037 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
torchbox:wagtailfrom 2.7 before 2.7.3
torchbox:wagtailfrom 2.8 before 2.8.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jjjr-3jcw-f8v6PyPIwagtail<2.7.32.7.3
GHSA-jjjr-3jcw-f8v6PyPIwagtail>=2.8rc1 <2.8.22.8.2
GHSA-jjjr-3jcw-f8v6PyPIwagtail>=2.9rc1 <2.92.9
PYSEC-2020-153PyPIwagtail>=2.7 <2.7.3
>=2.8 <2.8.2
2.7.3, 2.8.2

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON