CVE-2019-3401

MEDIUMNVD 5.35.3—Elevated

5.3

The ManageFilters.jspa resource in Jira before version 7.13.3 and from version 8.0.0 before version 8.1.1 allows remote attackers to enumerate usernames via an incorrect authorisation check.

CVSS v3: 5.3
EG Score: 5.3(medium)
EPSS: 98.5%
KEV: Not listed

Published

May 22, 2019

Last Modified

November 21, 2024

References (2)

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

Weakness Classification(1)

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

CWE-863Incorrect Authorization

Data Freshness Timeline

(refreshed 11× in last 7d / 19× 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-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-28 13:43 UTCepss_batch
2026-05-27 19:18 UTCEG score recompute
2026-05-27 19:18 UTCGHSA enrichment
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 16:47 UTCepss_batch

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

Nucleihttp/cves/2019/CVE-2019-3401.yaml
First seen Jan 1, 2019
Atlassian Jira <7.13.3/8.0.0-8.1.1 - Incorrect Authorization
Open source ↗

Frequently asked(5)

What is CVE-2019-3401?

CVE-2019-3401 is a medium vulnerability published on May 22, 2019. The ManageFilters.jspa resource in Jira before version 7.13.3 and from version 8.0.0 before version 8.1.1 allows remote attackers to enumerate usernames via an incorrect authorisation check.

When was CVE-2019-3401 disclosed?

CVE-2019-3401 was first published in the National Vulnerability Database on May 22, 2019, 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-3401 actively exploited?

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

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

CVE-2019-3401 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2019-3401?

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

Explore →

Is Your Infrastructure Affected by CVE-2019-3401?

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

Start Free Scan →Browse All CVEs

CVE-2019-3401

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(1)

Data Freshness Timeline

Publicly available exploits

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-3401?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same CWE)