CVE-2019-15002

MEDIUMNVD 4.34.3—Trending — 3 sources updated this week

4.3

An exploitable CSRF vulnerability exists in Atlassian Jira, from versions 7.6.4 to 8.1.0. The login form doesn’t require a CSRF token. As a result, an attacker can log a user into the system under an unexpected account.

CVSS v3: 4.3
EG Score: 4.3(medium)
EPSS: 35.9%
KEV: Not listed

Published

February 11, 2025

Last Modified

July 30, 2025

References (1)

security@atlassianhttps://jira.atlassian.com/browse/JRASERVER-67979

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 15× in last 7d / 16× 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-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-30 12:00 UTCEG score recompute
2026-05-30 12:00 UTCGHSA enrichment
2026-05-29 13:42 UTCepss_batch

Frequently asked(5)

What is CVE-2019-15002?

CVE-2019-15002 is a medium vulnerability published on February 11, 2025. An exploitable CSRF vulnerability exists in Atlassian Jira, from versions 7.6.4 to 8.1.0. The login form doesn’t require a CSRF token. As a result, an attacker can log a user into the system under an unexpected account.

When was CVE-2019-15002 disclosed?

CVE-2019-15002 was first published in the National Vulnerability Database on February 11, 2025, with the most recent update on July 30, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-15002 actively exploited?

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

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

CVE-2019-15002 has a CVSS v3 base score of 4.3 (NVD).

How do I remediate CVE-2019-15002?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-15002, 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-15002

Explore →

Is Your Infrastructure Affected by CVE-2019-15002?

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

Start Free Scan →Browse All CVEs

CVE-2019-15002

📅 Published

🔄 Last Modified

🔗 References (1)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-15002?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (1)

Frequently asked(5)

Related CVEs(same CWE)