CVE-2019-15002Network attack vector

Forced account login via missing CSRF token

Published Feb 11, 2025 · Updated Mar 13, 2025

CSRF in Atlassian Jira Server and Data Center 7.6.4 through 8.1.0 allows remote authenticated users to force an unintended login. The login form accepts credential submissions without requiring a CSRF token, so a cross-site request replaces the victim's intended session with an attacker-chosen account. Exploitation requires credentials for that account and causes the victim to use Jira under the wrong identity, exposing activity entered during that session.

CVSS severity4.3
Medium
EPSS probability0.32%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

CSRF in Atlassian Jira Server and Data Center 7.6.4 through 8.1.0 allows remote authenticated users to force an unintended login. The login form accepts credential submissions without requiring a CSRF token, so a cross-site request replaces the victim's intended session with an attacker-chosen account. Exploitation requires credentials for that account and causes the victim to use Jira under the wrong identity, exposing activity entered during that session.

The record

CVE
CVE-2019-15002
Published
Feb 11, 2025
Updated
Mar 13, 2025
Vendor
Atlassian
Product
Jira Server
Classifications
CWE-352
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 11, 2025CVE publishedPublication date reported by the CVE source.
  2. Mar 13, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=unspecified <8.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Atlassian · Jira Serverversion=unspecified <8.1.0
Atlassian · Jira Data Centerversion=unspecified <8.1.0

Published CVSS scores

4.3CISA-ADPCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo