CVE-2020-14181

CRITICALNVD 5.39.0▲
EchelonGraph scoreMEDIUM confidence

Score elevated to 9.0 because EPSS predicts 100% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
9.0EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • 103 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • High exploitation likelihood — EPSS 100%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 100%CVSS: 5.3Exploit: Metasploit · epss top5pct · epss high · public exploitExposed services: 103

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Affected versions of Atlassian Jira Server and Data Center allow an unauthenticated user to enumerate users via an Information Disclosure vulnerability in the /ViewUserHover.jspa endpoint. The affected versions are before version 7.13.6, from version 8.0.0 before 8.5.7, and from version 8.6.0 before 8.12.0.

Internet exposure · derived from Shodan data

103 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2020-14181, in our KEV-Exposure radar’s Shodan-derived sample.

across 27 countries (United States, Germany, United Kingdom, Finland, Iran, Islamic Republic of)top: jira
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
5.3
EG Score
9.0CRITICALmedium confidence
EG Risk
85
EG Risk 85/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
Severity90% × 45%
Exploitation100% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
100%
EPSS %ILE
99th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: weaponized) · 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

September 17, 2020

Last Modified

November 21, 2024

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 1× in last 7d / 6× 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.

  1. 2026-09-30 15:11 UTCEG score recompute
  2. 2026-09-22 14:43 UTCEPSS rescore
  3. 2026-09-21 20:28 UTCEPSS rescore
  4. 2026-09-12 14:56 UTCEPSS rescore
  5. 2026-09-06 13:44 UTCEPSS rescore
  6. 2026-09-05 15:24 UTCEPSS rescore
  7. 2026-09-02 14:08 UTCEPSS rescore
  8. 2026-08-30 19:14 UTCEPSS rescore
  9. 2026-08-28 21:37 UTCEPSS rescore
  10. 2026-08-19 17:00 UTCEPSS rescore
  11. 2026-08-06 13:43 UTCEPSS rescore
  12. 2026-08-05 19:14 UTCEPSS rescore
  13. 2026-08-03 10:32 UTCEPSS rescore
  14. 2026-08-02 02:23 UTCEPSS rescore
  15. 2026-08-01 04:12 UTCEPSS rescore
  16. 2026-07-30 16:24 UTCEPSS rescore
  17. 2026-07-30 01:27 UTCEPSS rescore
  18. 2026-07-24 14:14 UTCEPSS rescore
  19. 2026-07-23 01:49 UTCEG score recompute
  20. 2026-07-22 21:28 UTCEG score recompute▲ 3.70
  21. 2026-07-22 21:28 UTCGHSA enrichment
  22. 2026-07-06 16:25 UTCEPSS rescore
  23. 2026-07-06 16:25 UTCEPSS rescore
  24. 2026-06-30 23:20 UTCEPSS rescore
  25. 2026-06-30 23:20 UTCEPSS rescore
Show 25 more
  1. 2026-06-28 14:05 UTCEPSS rescore
  2. 2026-06-25 13:47 UTCEPSS rescore
  3. 2026-06-25 13:47 UTCEPSS rescore
  4. 2026-06-23 21:31 UTCEPSS rescore
  5. 2026-06-23 21:31 UTCEPSS rescore
  6. 2026-06-17 17:50 UTCEPSS rescore
  7. 2026-06-17 17:50 UTCEPSS rescore
  8. 2026-06-16 17:50 UTCEPSS rescore
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-15 17:46 UTCEPSS rescore
  11. 2026-06-12 23:09 UTCEPSS rescore
  12. 2026-06-10 13:20 UTCEPSS rescore
  13. 2026-06-08 14:15 UTCEPSS rescore
  14. 2026-06-08 14:15 UTCEPSS rescore
  15. 2026-06-06 13:45 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-06 13:45 UTCEPSS rescore
  18. 2026-06-05 22:45 UTCEPSS rescore
  19. 2026-06-05 22:45 UTCEPSS rescore
  20. 2026-05-31 00:15 UTCEPSS rescore
  21. 2026-05-31 00:14 UTCEPSS rescore
  22. 2026-05-26 13:42 UTCEPSS rescore
  23. 2026-05-26 13:42 UTCEPSS rescore
  24. 2026-05-23 07:43 UTCEG score recompute
  25. 2026-05-23 07:43 UTCGHSA enrichment

Publicly available exploits

(5 references)

Working exploit code is in the public domain (1 Metasploit module) (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitauxiliary/scanner/http/jira_user_enum✓ verified
    First seen Aug 16, 2020

    Jira Users Enumeration

    Open source ↗
  • Exploit-DBEDB-49633
    First seen Mar 10, 2021

    Atlassian JIRA 8.11.1 - User Enumeration

    Open source ↗
  • GitHub PoCbk-rao/CVE-2020-14181
    First seen Feb 5, 2021

    Poc for CVE-2020-14181

    Open source ↗
  • GitHub PoCRival420/CVE-2020-14181
    First seen Oct 26, 2020

    POC For CVE-2020-1481 - Jira Username Enumerator/Validator

    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-14181.yaml
    First seen Jan 1, 2020

    Jira Server and Data Center - Information Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-14181?
CVE-2020-14181 is a critical vulnerability published on September 17, 2020. Affected versions of Atlassian Jira Server and Data Center allow an unauthenticated user to enumerate users via an Information Disclosure vulnerability in the /ViewUserHover.jspa endpoint. The affected versions are before version 7.13.6, from version 8.0.0 before 8.5.7, and from version 8.6.0…
When was CVE-2020-14181 disclosed?
CVE-2020-14181 was first published on September 17, 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-14181 actively exploited?
CVE-2020-14181 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 100% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-14181?
CVE-2020-14181 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2020-14181?
No fix for CVE-2020-14181 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-14181

Explore →

Is Your Infrastructure Affected by CVE-2020-14181?

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

Book a Demo →Browse All CVEs