CVE-2020-11037

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (14th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

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.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity61% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
14th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 30, 2020

Last Modified

November 21, 2024

References (6)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
wagtail2.7, 2.7.1, 2.7.2, 2.8, 2.8.1
  • every version up to 2.7.3: fixed in 2.7.3
  • 2.8rc1 up to 2.8.2: fixed in 2.8.2
  • 2.9rc1 up to 2.9: fixed in 2.9
  • 2.7 up to 2.7.3: fixed in 2.7.3
  • 2.8 up to 2.8.2: fixed in 2.8.2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 169 total refreshes for this CVE.

  1. 2026-10-09 20:03 UTCEPSS rescore
  2. 2026-10-08 16:38 UTCEPSS rescore
  3. 2026-10-07 23:43 UTCEPSS rescore
  4. 2026-10-06 15:13 UTCEPSS rescore
  5. 2026-10-05 17:39 UTCEPSS rescore
  6. 2026-10-04 23:18 UTCEPSS rescore
  7. 2026-10-03 14:22 UTCEPSS rescore
  8. 2026-09-30 14:59 UTCEPSS rescore
  9. 2026-09-30 10:32 UTCEG score recompute
  10. 2026-09-27 13:40 UTCEPSS rescore
  11. 2026-09-27 04:15 UTCOSV refresh
  12. 2026-09-26 15:54 UTCEPSS rescore
  13. 2026-09-26 00:20 UTCEPSS rescore
  14. 2026-09-24 13:59 UTCEPSS rescore
  15. 2026-09-22 14:43 UTCEPSS rescore
  16. 2026-09-21 20:28 UTCEPSS rescore
  17. 2026-09-20 20:11 UTCEPSS rescore
  18. 2026-09-19 15:37 UTCEPSS rescore
  19. 2026-09-18 19:23 UTCEPSS rescore
  20. 2026-09-17 19:22 UTCEPSS rescore
  21. 2026-09-16 14:04 UTCEPSS rescore
  22. 2026-09-16 14:04 UTCEPSS rescore
  23. 2026-09-15 03:06 UTCEPSS rescore
  24. 2026-09-13 16:42 UTCEPSS rescore
  25. 2026-09-12 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:48 UTCEPSS rescore
  2. 2026-09-11 09:32 UTCEPSS rescore
  3. 2026-09-07 15:57 UTCEPSS rescore
  4. 2026-09-07 13:47 UTCOSV refresh
  5. 2026-09-06 13:44 UTCEPSS rescore
  6. 2026-09-05 15:24 UTCEPSS rescore
  7. 2026-09-04 13:56 UTCEPSS rescore
  8. 2026-09-04 05:03 UTCEPSS rescore
  9. 2026-09-02 14:08 UTCEPSS rescore
  10. 2026-09-01 03:32 UTCEPSS rescore
  11. 2026-08-30 19:14 UTCEPSS rescore
  12. 2026-08-30 01:18 UTCEPSS rescore
  13. 2026-08-28 21:37 UTCEPSS rescore
  14. 2026-08-27 14:21 UTCEPSS rescore
  15. 2026-08-26 14:42 UTCEPSS rescore
  16. 2026-08-25 13:45 UTCEPSS rescore
  17. 2026-08-20 22:51 UTCEPSS rescore
  18. 2026-08-20 22:45 UTCOSV refresh
  19. 2026-08-19 17:00 UTCEPSS rescore
  20. 2026-08-18 13:44 UTCEPSS rescore
  21. 2026-08-17 13:43 UTCEPSS rescore
  22. 2026-08-16 14:52 UTCEPSS rescore
  23. 2026-08-16 02:11 UTCEPSS rescore
  24. 2026-08-15 01:26 UTCEPSS rescore
  25. 2026-08-13 21:57 UTCEPSS rescore
  26. 2026-08-12 13:47 UTCEPSS rescore
  27. 2026-08-09 13:43 UTCEPSS rescore
  28. 2026-08-08 16:33 UTCEPSS rescore
  29. 2026-08-07 16:23 UTCEPSS rescore
  30. 2026-08-06 13:43 UTCEPSS rescore
  31. 2026-08-05 19:14 UTCEPSS rescore
  32. 2026-08-05 14:11 UTCOSV refresh
  33. 2026-08-04 15:06 UTCEPSS rescore
  34. 2026-08-04 10:34 UTCEPSS rescore
  35. 2026-08-03 10:32 UTCEPSS rescore
  36. 2026-08-02 02:23 UTCEPSS rescore
  37. 2026-08-01 04:12 UTCEPSS rescore
  38. 2026-07-30 16:24 UTCEPSS rescore
  39. 2026-07-30 01:27 UTCEPSS rescore
  40. 2026-07-28 15:32 UTCEPSS rescore
  41. 2026-07-26 14:51 UTCEPSS rescore
  42. 2026-07-25 14:14 UTCEPSS rescore
  43. 2026-07-24 14:14 UTCEPSS rescore
  44. 2026-07-23 14:15 UTCEPSS rescore
  45. 2026-07-23 14:15 UTCEPSS rescore
  46. 2026-07-23 01:48 UTCEG score recompute
  47. 2026-07-22 22:32 UTCEG score recompute
  48. 2026-07-22 14:05 UTCEPSS rescore
  49. 2026-07-21 15:22 UTCEPSS rescore
  50. 2026-07-21 15:22 UTCEPSS rescore
  51. 2026-07-20 17:04 UTCEPSS rescore
  52. 2026-07-19 14:28 UTCEPSS rescore
  53. 2026-07-19 14:28 UTCEPSS rescore
  54. 2026-07-19 13:24 UTCOSV refresh
  55. 2026-07-19 02:26 UTCEPSS rescore
  56. 2026-07-19 02:26 UTCEPSS rescore
  57. 2026-07-18 10:02 UTCEPSS rescore
  58. 2026-07-16 16:59 UTCEPSS rescore
  59. 2026-07-16 16:59 UTCEPSS rescore
  60. 2026-07-15 16:55 UTCEPSS rescore
  61. 2026-07-13 22:27 UTCEPSS rescore
  62. 2026-07-13 06:10 UTCEPSS rescore
  63. 2026-07-13 06:10 UTCEPSS rescore
  64. 2026-07-12 05:44 UTCEPSS rescore
  65. 2026-07-11 08:24 UTCEPSS rescore
  66. 2026-07-09 19:06 UTCEPSS rescore
  67. 2026-07-08 15:11 UTCEPSS rescore
  68. 2026-07-07 13:43 UTCEPSS rescore
  69. 2026-07-06 16:25 UTCEPSS rescore
  70. 2026-07-06 16:25 UTCEPSS rescore
  71. 2026-07-06 02:20 UTCEPSS rescore
  72. 2026-07-05 02:27 UTCEPSS rescore
  73. 2026-07-04 06:28 UTCEPSS rescore
  74. 2026-07-01 22:31 UTCOSV refresh
  75. 2026-07-01 15:03 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2020-11037?
CVE-2020-11037 is a medium vulnerability published on April 30, 2020. 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…
When was CVE-2020-11037 disclosed?
CVE-2020-11037 was first published on April 30, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-11037 actively exploited?
CVE-2020-11037 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-11037?
CVE-2020-11037 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2020-11037?
A fix for CVE-2020-11037 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-11037

Explore →

Is Your Infrastructure Affected by CVE-2020-11037?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs