vciy

CVE-2020-25200

INDEX BUILT · 2026-09-20

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.

Pritunl 1.29.2145.25 allows attackers to enumerate valid VPN usernames via a series of /auth/session login attempts

CVE-2020-252003 of 4 sources documented this
33

rank 33 = 16 + 13 + 2 + 2 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.07470  ·  without this subject the record ranks 17

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from NVD  ·  without this subject the record ranks 20

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-12-23  ·  without this subject the record ranks 31

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 31

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 33

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$89,600over the next 30 days, if this record is yours
Movement+$209,000on 2025-03-26, the last material move, 1 year, 2 months before this reading
Basisassumeda published average, not your estate

$89,600 = $4.99M incident cost x 0.24048551839932833 exposure x 0.0747 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

0.0747EPSSNOT IN KEVas of 2026-09-20
Severity5.3 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseno fix version held
Movementthreshold crossedreceipt
RISING10Risen from 0.0363 to 0.0747 across 22 observations. arc-rules@v1

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.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Check a version against this record

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.

What counts as a move

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 affectedMitigated

Choose 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.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactPartial confidentiality lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-203 Observable Discrepancyreceipt
Published consequencesCWE-203: Confidentiality, Access Control: Read Application Data, Bypass Protection Mechanism; Confidentiality: Read Application Data[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 15 Jun 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2020-09-06.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2020-09-06receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD5.3 MEDIUMreceipt
Exploit probability0.0747 · top 6% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes25 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesPritunlreceipt
Published rangespritunl 1.29.2145.25receipt

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.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Pritunl 1.29.2145.25 allows attackers to enumerate valid VPN usernames via a series of /auth/session login attempts. Initially, the server will return error 401. However, if the username is valid, then after 20 login attempts, the server will start responding with error 400. Invalid usernames will receive error 401 indefinitely. Note: This has been disputed by the vendor as not a vulnerability. They argue that this is an intended design receipt

NVD's analysis a second authority

severity
5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
weakness
CWE-203
affected versions
pritunl 1.29.2145.25

check it yourself pritunl.com pritunl.com github.com receipt

Dated events

2023-03-07EPSS moved 0.06 to 0.002026-06-15EPSS moved 0.73 to 0.07

Movement the material steps

14 Apr 20210.0363
7 Mar 20230.00119 · scoring model v2023.03.01
17 Mar 20250.37887 · crossed 0.10 · scoring model v2025.03.14
19 Mar 20250.55305 · crossed 0.50
20 Mar 20250.37887 · crossed 0.50
26 Mar 20250.55305 · crossed 0.50
27 Mar 20250.65315
28 Mar 20250.55305
23 Dec 20250.6809
18 Feb 20260.5739
20 May 20260.69204
15 Jun 20260.0747 · crossed 0.10 and 0.50 · scoring model v2026.06.15
Show all 22 observations
14 Apr 20210.0363
4 Feb 20220.05736
7 Mar 20230.00119
8 May 20230.00144
17 Jun 20230.00164
17 Dec 20240.00182
17 Mar 20250.37887
19 Mar 20250.55305
20 Mar 20250.37887
26 Mar 20250.55305
27 Mar 20250.65315
28 Mar 20250.55305
29 Mar 20250.56459
30 Mar 20250.55305
23 Dec 20250.6809
18 Jan 20260.62652
31 Jan 20260.64443
16 Feb 20260.62249
18 Feb 20260.5739
20 May 20260.69204
21 May 20260.72966
15 Jun 20260.0747

22 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

EPSS 0.0747Public PoC2020-09-06Published2020-10-01Index as of2026-06-15

The record had been public for 5 years, 8 months when this index was last written.

Public PoC 2020-09-06 receipt · Published 2020-10-01 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2020-25200.

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.

Everything on this page is free. Public data. Withholding it protects nothing.