Skip to content
Fencer Vulns
critical 9.4

CVE-2023-22501 in the critical feed json

An authentication vulnerability was discovered in Jira Service Management Server and Data Center which allows an attacker to impersonate an…

published 2023-02-01 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-26641

cvss
9.4
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
15.5%
EPSS 15.5% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

An authentication vulnerability was discovered in Jira Service Management Server and Data Center which allows an attacker to impersonate another user and gain access to a Jira Service Management instance under certain circumstances_._ With write access to a User Directory and outgoing email enabled on a Jira Service Management instance, an attacker could gain access to signup tokens sent to users with accounts that have never been logged into. Access to these tokens can be obtained in two cases:

* If the attacker is included on Jira issues or requests with these users, or * If the attacker is forwarded or otherwise gains access to emails containing a “View Request” link from these users.

Bot accounts are particularly susceptible to this scenario. On instances with single sign-on, external customer accounts can be affected in projects where anyone can create their own account.

Patch / fix

  • Atlassian Jira Service Management Data Center before 5.3.0
  • Atlassian Jira Service Management Server before 5.3.0
  • atlassian jira_service_management 5.3.3, 5.4.2

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2 y ago

Exploit prediction

15.53% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 9.4 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • Atlassian Jira Service Management Data Center
  • Atlassian Jira Service Management Server
  • atlassian jira_service_management

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.