LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39125: Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to discover the...

Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to discover the usernames of users via an enumeration vulnerability in the password reset page. The affected versions are before version 8.5.10, and from version 8.6.0 before 8.13.1.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

An unauthenticated person could use Jira's password reset page to learn whether usernames exist. This does not let them log in, change data, or disrupt service by itself, but it reduces anonymity and can support phishing, credential stuffing, or targeted attacks against Jira accounts.

Executive priority

Treat this as a moderate confidentiality issue. It is unlikely to be a standalone breach path, but it can make account attacks more effective. Patch during normal vulnerability remediation, faster for public Jira systems.

Technical view

CVE-2021-39125 is a username enumeration flaw in Atlassian Jira Server and Data Center. The affected ranges are versions before 8.5.10 and versions from 8.6.0 before 8.13.1. CVSS 3.1 is 5.3, network reachable, low complexity, no privileges or user interaction required, with low confidentiality impact.

Likely exposure

Exposure is most relevant for internet-facing or partner-accessible Jira Server and Data Center instances running the listed affected versions. Internal-only systems still matter if many users or contractors can reach the password reset page.

Exploitation context

The provided sources do not show active exploitation, and this CVE is not marked as CISA KEV. The issue is still practical because anonymous access is enough and confirmed usernames can improve later social engineering or password attacks.

Researcher notes

The source bundle names username discovery through the password reset page but does not include request details, proof-of-concept material, or broader impact claims. Keep analysis scoped to enumeration and affected version validation.

Mitigation direction

  • Upgrade Jira Server or Data Center beyond the affected version ranges.
  • Prioritize internet-facing Jira instances and environments with many external users.
  • Review Atlassian guidance for fixed versions and any configuration-specific advice.
  • Reduce unnecessary anonymous exposure to Jira account recovery pages where operationally possible.

Validation and detection

  • Inventory Jira Server and Data Center versions across production and non-production.
  • Confirm no instance runs before 8.5.10 or from 8.6.0 before 8.13.1.
  • Check whether password reset pages are reachable anonymously from untrusted networks.
  • Review access logs for unusual password reset enumeration patterns.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-39125 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2021-39125Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianJira Serverunspecified, 8.6.0, unspecifiedListed
AtlassianJira Data Centerunspecified, 8.6.0, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.