CVE-2019-8449

MEDIUMNVD 5.39.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 85% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
5.3
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 85%
CISA-KEV: Not listedEPSS: 85%CVSS: 5.3Exploit: NoneExposed: 0

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

The /rest/api/latest/groupuserpicker resource in Jira before version 8.4.0 allows remote attackers to enumerate usernames via an information disclosure vulnerability.

CVSS v3
5.3
EG Score
9.0(high)
EG Risk
79(Track)
EG Risk 79/100SSVC: Track

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%
Exploitation85% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.7%
KEV
Not listed

Published

September 11, 2019

Last Modified

November 21, 2024

References (4)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 22× 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-07-23 01:47 UTCEG score recompute▲ 3.70
  2. 2026-07-22 22:29 UTCEG score recompute
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-18 10:02 UTCEPSS rescore
  7. 2026-07-15 16:55 UTCEPSS rescore
  8. 2026-07-13 06:10 UTCEPSS rescore
  9. 2026-07-13 06:10 UTCEPSS rescore
  10. 2026-07-09 19:06 UTCEPSS rescore
  11. 2026-07-07 13:43 UTCEPSS rescore
  12. 2026-07-06 16:25 UTCEPSS rescore
  13. 2026-07-06 16:25 UTCEPSS rescore
  14. 2026-07-04 06:28 UTCEPSS rescore
  15. 2026-07-01 15:03 UTCEPSS rescore
  16. 2026-07-01 15:03 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-21 14:54 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-17 17:50 UTCEPSS rescore
Show 27 more
  1. 2026-06-15 17:46 UTCEPSS rescore
  2. 2026-06-14 23:15 UTCEPSS rescore
  3. 2026-06-14 23:15 UTCEPSS rescore
  4. 2026-06-13 22:58 UTCEPSS rescore
  5. 2026-06-12 23:09 UTCEPSS rescore
  6. 2026-06-12 23:09 UTCEPSS rescore
  7. 2026-06-10 22:16 UTCEPSS rescore
  8. 2026-06-10 22:16 UTCEPSS rescore
  9. 2026-06-10 13:19 UTCEPSS rescore
  10. 2026-06-07 15:23 UTCEPSS rescore
  11. 2026-06-07 15:23 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-06 13:45 UTCEPSS rescore
  14. 2026-06-05 22:45 UTCEPSS rescore
  15. 2026-06-05 06:08 UTCEPSS rescore
  16. 2026-06-04 13:10 UTCEPSS rescore
  17. 2026-06-04 13:10 UTCEPSS rescore
  18. 2026-06-01 13:50 UTCEPSS rescore
  19. 2026-06-01 13:50 UTCEPSS rescore
  20. 2026-05-31 00:14 UTCEPSS rescore
  21. 2026-05-31 00:14 UTCEPSS rescore
  22. 2026-05-29 13:42 UTCEPSS rescore
  23. 2026-05-27 14:43 UTCEG score recompute
  24. 2026-05-27 14:43 UTCGHSA enrichment
  25. 2026-05-27 13:39 UTCEPSS rescore
  26. 2026-05-27 13:38 UTCEPSS rescore
  27. 2026-05-24 16:47 UTCEPSS rescore

Publicly available exploits

(4 references)

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

  • GitHub PoCr0lh/CVE-2019-8449
    First seen Feb 14, 2020

    User Enumeration Proof Of Concept Exploit for CVE-2019-8449

    Open source ↗
  • Exploit-DBEDB-47990
    First seen Feb 3, 2020

    Jira 8.3.4 - Information Disclosure (Username Enumeration)

    Open source ↗
  • GitHub PoCmufeedvh/CVE-2019-8449
    First seen Feb 2, 2020

    CVE-2019-8449 Exploit for Jira v2.1 - v8.3.4

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

    Jira <8.4.0 - Information Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-8449?
CVE-2019-8449 is a medium vulnerability published on September 11, 2019. The /rest/api/latest/groupuserpicker resource in Jira before version 8.4.0 allows remote attackers to enumerate usernames via an information disclosure vulnerability.
When was CVE-2019-8449 disclosed?
CVE-2019-8449 was first published in the National Vulnerability Database on September 11, 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-8449 actively exploited?
CVE-2019-8449 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-8449?
CVE-2019-8449 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.
How do I remediate CVE-2019-8449?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-8449, 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

Explore the affected products and dependency analysis for CVE-2019-8449

Explore →

Is Your Infrastructure Affected by CVE-2019-8449?

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

Start Free Scan →Browse All CVEs