Skip to content
Fencer Vulns
medium 6.1

CVE-2020-11037 json

Potential Observable Timing Discrepancy in Wagtail

published 2020-04-30 6 y ago modified 2026-07-08 4 mo ago also GHSA-jjjr-3jcw-f8v6 , PYSEC-2020-153 , EUVD-2020-0236

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi wagtail 2.7.3, 2.8.2, 2.9
  • torchbox wagtail 2.7.3, 2.8.2

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N
NVD 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi wagtail
<2.7.3
>=2.8rc1, <2.8.2
>=2.9rc1, <2.9
>=2.7, <2.7.3
>=2.8, <2.8.2
2.7.3
2.8.2
2.9

Affected products

  • wagtail Wagtail

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.