# CVE-2020-11037: Potential Observable Timing Discrepancy in Wagtail

Source: https://junglewise.ai/threats/cve-2020-11037-potential-observable-timing-discrepancy-in-wagtail  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2020-04-30  
License: CC BY 4.0 with a link back

CVE-2020-11037 · Severity: low · CVSS 3.1 · Published 2020-04-30

In Wagtail before versions 2.7.2 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. 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.

Technologies: [wagtail (PyPI)](https://junglewise.ai/threats/technologies/pypi-wagtail). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2020-11037 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2020-11037 being exploited in the wild.

**How severe is CVE-2020-11037?** Low severity, with a CVSS score of 3.1, published 30 April 2020.

**Which products and versions are affected?** wagtail (PyPI) ECOSYSTEM:introduced=0,fixed=2.7.3, ECOSYSTEM:introduced=2.7,fixed=2.7.3,introduced=2.8,fixed=2.8.2.

**Is there a fix for CVE-2020-11037?** Yes. wagtail (PyPI): upgrade to 2.7.3, 2.8.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2020-11037?** Check whether you run wagtail (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- wagtail (PyPI): upgrade to 2.7.3, 2.8.2 or later

  ```sh
  pip install "wagtail>=2.8.2"
  ```


## Affected products

- wagtail (PyPI) ECOSYSTEM:introduced=0,fixed=2.7.3, ECOSYSTEM:introduced=2.7,fixed=2.7.3,introduced=2.8,fixed=2.8.2

## Identifiers

- CVE-2020-11037
- GHSA-jjjr-3jcw-f8v6
- PYSEC-2020-153

## Related threats

- [Wagtail Pages admin API improper access control](https://junglewise.ai/threats/cve-2026-55468-wagtail-pages-admin-api-improper-access-control)
- [PYSEC-2026-2030 - Wagtail has improper permission handling on admin preview endpoints](https://junglewise.ai/threats/cve-2026-25517-wagtail-has-improper-permission-handling-on-admin-preview)
- [PYSEC-2026-2032 - Improper Handling of Insufficient Permissions in `wagtail.contrib.settings`](https://junglewise.ai/threats/cve-2024-35228-improper-handling-of-insufficient-permissions-in-wagtail-contrib)
- [PYSEC-2026-2031 - Wagtail has permission check bypass when editing a model with per-field restrictions through…](https://junglewise.ai/threats/cve-2024-32882-wagtail-has-permission-check-bypass-when-editing-a-model-with-per)
- [Wagtail reflected XSS in dynamic image URL generator](https://junglewise.ai/threats/cve-2026-54263-wagtail-reflected-xss-in-dynamic-image-url-generator)