LiveActive security incident?Get immediate response
CVE Record

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

Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to the query component JQL endpoint via a Broken Access Control vulnerability (BAC) vulnerability. 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

This issue affects Atlassian Jira Server and Jira Data Center. An unauthenticated remote attacker could access the JQL query component endpoint through broken access control, with limited integrity impact. It is not listed as KEV in the provided bundle, and no active exploitation evidence is cited.

Executive priority

Schedule remediation in normal vulnerability management timelines, accelerated for internet-facing Jira. Business risk is moderate because authentication is not required, but the cited impact is limited to integrity and no active exploitation is evidenced.

Technical view

CVE-2021-39127 is a broken access control flaw in the Jira query component JQL endpoint. Affected ranges are before 8.5.10 and 8.6.0 through before 8.13.1. CVSS 3.1 is 5.3, network-accessible, low complexity, no privileges, no user interaction, integrity impact only.

Likely exposure

Organizations running Jira Server or Jira Data Center in the affected version ranges are potentially exposed, especially if Jira is reachable from the internet or untrusted networks. Atlassian Cloud is not identified in the provided sources.

Exploitation context

The source bundle supports unauthenticated remote reachability but does not cite public exploitation, KEV listing, exploit code, or observed attacks. Treat exploitation status as unconfirmed rather than active.

Researcher notes

The bundle provides limited technical detail and no CWE mapping. Focus validation on product edition, version range, exposure path, and anonymous access behavior. Avoid assuming broader Jira components or Atlassian Cloud are affected without vendor evidence.

Mitigation direction

  • Upgrade Jira Server/Data Center outside affected ranges per Atlassian guidance.
  • Prioritize internet-facing or broadly accessible Jira instances first.
  • Restrict Jira access to trusted networks where operationally feasible.
  • Review Atlassian JRASERVER-72003 for vendor-specific remediation details.

Validation and detection

  • Inventory Jira Server and Data Center versions across all environments.
  • Confirm whether any instance is before 8.5.10 or 8.6.0 before 8.13.1.
  • Check whether affected instances are reachable by unauthenticated users.
  • Review access logs for unusual anonymous JQL endpoint activity.
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.

cve · low confidence lookup

CVE-2021-39127 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:N/I:L/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:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.