CVE-2019-20401

MEDIUMNVD 6.56.5—

6.5

Various installation setup resources in Jira before version 8.5.2 allow remote attackers to configure a Jira instance, which has not yet finished being installed, via Cross-site request forgery (CSRF) vulnerabilities.

CVSS v3: 6.5
EG Score: 6.5(medium)
EPSS: 55.9%
KEV: Not listed

Published

February 6, 2020

Last Modified

November 21, 2024

References (2)

security@atlassianhttps://jira.atlassian.com/browse/JRASERVER-70406
af854a3a-2127-422b-91ae-364da2661108https://jira.atlassian.com/browse/JRASERVER-70406

Weakness Classification(1)

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

CWE-352Cross-Site Request Forgery (CSRF)

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 22:45 UTCepss_batch
2026-06-05 22:45 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 08:13 UTCEG score recompute
2026-05-27 08:13 UTCGHSA enrichment
2026-05-26 13:42 UTCepss_batch

Frequently asked(5)

What is CVE-2019-20401?

CVE-2019-20401 is a medium vulnerability published on February 6, 2020. Various installation setup resources in Jira before version 8.5.2 allow remote attackers to configure a Jira instance, which has not yet finished being installed, via Cross-site request forgery (CSRF) vulnerabilities.

When was CVE-2019-20401 disclosed?

CVE-2019-20401 was first published in the National Vulnerability Database on February 6, 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-2019-20401 actively exploited?

CVE-2019-20401 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 55.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-20401?

CVE-2019-20401 has a CVSS v3 base score of 6.5 (NVD).

How do I remediate CVE-2019-20401?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-20401, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-20401

Explore →

Is Your Infrastructure Affected by CVE-2019-20401?

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

Start Free Scan →Browse All CVEs

CVE-2019-20401

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-20401?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same CWE)