CVE-2020-11037
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
Potential Observable Timing Discrepancy in Wagtail
rank 16 = 0 + 12 + 0 + 4 + 0
rank@v1 · backlog
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.00250 · without this subject the record ranks 16
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 4.7, from NVD · without this subject the record ranks 4
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
no persisting rise in 365 days · without this subject the record ranks 16
How much of the world it touches
NVD CPE configurations
2 products in the CPE ranges · without this subject the record ranks 12
Someone else already set the date
CISA KEV remediation due date
no CISA due date · without this subject the record ranks 16
$8,960 = $4.99M incident cost x 0.7179585840212677 exposure x 0.0025 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
Hindsight · the state
Foresight · where to check next
No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.
Sources disagree here.
Both shown, dated. We don't pick winners. disagreement-rules@v1
Running Wagtail? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Set up a watchlist (needs a Practitioner account)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
AcceptDeferPatch by…Not affectedMitigatedChoose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Nothing observed in held sources.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published
- RUNG 3Exploited in the wild · CISA KEV listed
- RUNG 4Ransomware campaign use known
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
Attack path
What it is stated by the CNA
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. receipt
Read the rest of the CNA's description
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.
NVD's analysis a second authority
- severity
- 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- weakness
- CWE-208; CWE-362
- affected versions
- torchbox wagtail >= 2.7 < 2.7.3; torchbox wagtail >= 2.8 < 2.8.2
- also scored by
- [email protected] 6.1 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N
The CNA scored it 6.1 and NVD 4.7. Both are shown because both were published; we do not pick one.
check it yourself github.com github.com github.com github.com github.com receipt
Movement the material steps
Show all 13 observations
13 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The full biography
The record had been public for 6 years, 1 month when this index was last written.
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.
Browse the index from here
These are index-wide views, not findings about CVE-2020-11037.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.