How severe is CVE-2019-8448?

CVE-2019-8448 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2019-8448 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (76th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-8448?

CVE-2019-8448 affects Atlassian Jira Server. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-8448?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2019-8448 published?

CVE-2019-8448 was published on 2019-08-13 and last updated on 2026-06-17.

CVE-2019-8448

CVE-2019-8448 is a medium-severity vulnerability in Atlassian Jira Server with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
CVSS v2: 5.0
EPSS exploit prediction: 2% (76th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Atlassian Jira Server
Published: 2019-08-13
Last modified: 2026-06-17

Description

The login.jsp resource in Jira before version 7.13.4, and from version 8.0.0 before version 8.2.2 allows remote attackers to enumerate usernames via an information disclosure vulnerability.

Frequently asked questions

What is CVE-2019-8448?: The login.jsp resource in Jira before version 7.13.4, and from version 8.0.0 before version 8.2.2 allows remote attackers to enumerate usernames via an information disclosure vulnerability.
How severe is CVE-2019-8448?: CVE-2019-8448 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2019-8448 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (76th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-8448?: CVE-2019-8448 affects Atlassian Jira Server. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-8448?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-8448 published?: CVE-2019-8448 was published on 2019-08-13 and last updated on 2026-06-17.

References

https://jira.atlassian.com/browse/JRASERVER-69797

Affected products (1)

cpe:2.3:a:atlassian:jira_server:*:*:*:*:*:*:*:*

More vulnerabilities in Atlassian Jira Server

CVE-2022-26136 — Critical (CVSS 9.8): A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to bypass Servlet Filters used…
CVE-2022-0540 — Critical (CVSS 9.8): A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a…
CVE-2019-11581 — Critical (CVSS 9.8): There was a server-side template injection vulnerability in Jira Server and Data Center, in the ContactAdministrators…
CVE-2025-22157 — High (CVSS 8.8): This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions: 9.12.0, 10.3.0, 10.4.0,…
CVE-2024-21683 — High (CVSS 8.8): This High severity RCE (Remote Code Execution) vulnerability was introduced in version 5.2 of Confluence Data Center…
CVE-2022-26137 — High (CVSS 8.8): A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to cause additional Servlet…

All CVEs affecting Atlassian Jira Server →