CVE-2019-15002: CSRF
First published: Tue Feb 11 2025(Updated: )
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.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira | >=7.6.4<=8.1.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-15002?
CVE-2019-15002 is classified as a critical severity vulnerability due to its ability to bypass authentication.
How do I fix CVE-2019-15002?
To fix CVE-2019-15002, upgrade Atlassian Jira to a version above 8.1.0.
What versions of Atlassian Jira are affected by CVE-2019-15002?
CVE-2019-15002 affects Atlassian Jira versions from 7.6.4 to 8.1.0.
What type of vulnerability is CVE-2019-15002?
CVE-2019-15002 is a Cross-Site Request Forgery (CSRF) vulnerability.
Can CVE-2019-15002 be exploited remotely?
Yes, CVE-2019-15002 can be exploited remotely, allowing attackers to authenticate as other users.
- agent/weakness
- agent/references
- agent/description
- agent/type
- agent/first-publish-date
- agent/author
- agent/source
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/severity
- agent/last-modified-date
- agent/event
- vendor/atlassian
- canonical/atlassian jira