CVE-2023-22501Network attack vector

User impersonation via exposed signup tokens

Published Feb 1, 2023 · Updated Oct 1, 2024

Broken authentication in Atlassian Jira Service Management allows remote attackers to impersonate users through exposed signup tokens. The signup-token workflow places tokens for never-used accounts in View Request links that issue participants or forwarded-email recipients can obtain. Exploitation requires outgoing email plus User Directory write access or access to such a link; success grants account access and permits silent password setting.

CVSS severity9.4
Critical
EPSS probability15.53%
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

Broken authentication in Atlassian Jira Service Management allows remote attackers to impersonate users through exposed signup tokens. The signup-token workflow places tokens for never-used accounts in View Request links that issue participants or forwarded-email recipients can obtain. Exploitation requires outgoing email plus User Directory write access or access to such a link; success grants account access and permits silent password setting.

The record

CVE
CVE-2023-22501
Published
Feb 1, 2023
Updated
Oct 1, 2024
Vendor
Atlassian
Product
Jira Service Management Server
Classifications
CWE-287, T1078
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 1, 2023CVE publishedPublication date reported by the CVE source.
  2. Oct 1, 2024Record 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=before 5.3.3
  2. Affected versionversion=before 5.4.2
  3. Affected versionversion=before 5.5.1
  4. Affected versionversion=before 5.6.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Atlassian · Jira Service Management Serverversion=before 5.3.3; version=before 5.4.2; version=before 5.5.1; version=before 5.6.0
Atlassian · Jira Service Management Data Centerversion=before 5.3.3; version=before 5.4.2; version=before 5.5.1; version=before 5.6.0
Atlassian · Jira Service Managementversion=5.3.0 <5.3.3; version=5.4.0 <5.4.2; version=5.5.0

Published CVSS scores

9.1NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
9.4AtlassianCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

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
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-287Improper Authentication
T1078Valid Accounts

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