LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41311: Affected versions of Atlassian Jira Server and Data Center allow attackers with access to an administrator...

Affected versions of Atlassian Jira Server and Data Center allow attackers with access to an administrator account that has had its access revoked to modify projects' Users & Roles settings, via a Broken Authentication vulnerability in the /plugins/servlet/project-config/PROJECT/roles endpoint. The affected versions are before version 8.19.1.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue affects Atlassian Jira Server and Data Center before 8.19.1. A revoked administrator account could still modify project Users & Roles settings, creating a business risk around unauthorized permission changes and project access manipulation.

Executive priority

Prioritize remediation for any self-managed Jira instance below 8.19.1, especially where administrator turnover or shared admin accounts exist. The main business risk is unauthorized project permission modification, not system takeover based on the supplied evidence.

Technical view

CVE-2021-41311 is a broken authentication flaw in Jira Server/Data Center before 8.19.1. The affected endpoint is /plugins/servlet/project-config/PROJECT/roles, where a revoked administrator account could modify project role settings. CVSS 3.1 is 7.5, driven by high integrity impact.

Likely exposure

Exposure is limited to organizations running Jira Server or Jira Data Center versions before 8.19.1. The source bundle does not identify specific deployment configurations, plugins, or cloud products as affected.

Exploitation context

The bundle does not report active exploitation, and CISA KEV status is false. The described attacker condition is unusual: access to an administrator account whose access was revoked. Treat it as an integrity risk around project permissions.

Researcher notes

Evidence names the vulnerable endpoint and affected products but does not provide detailed exploit prerequisites beyond revoked administrator account access. The CVSS vector lists PR:N, which appears inconsistent with the textual attacker condition; treat the narrative source as controlling.

Mitigation direction

  • Upgrade Jira Server or Data Center to 8.19.1 or later, following Atlassian guidance.
  • Check Atlassian JRASERVER-72802 for current vendor notes and supported upgrade paths.
  • Review administrator account revocation procedures for Jira environments.
  • Audit project Users & Roles settings for unexpected or unauthorized changes.

Validation and detection

  • Inventory Jira Server and Data Center instances and record installed versions.
  • Confirm no affected instance is running a version before 8.19.1.
  • Review Jira audit logs for project role changes by revoked or former administrators.
  • Verify administrator deprovisioning includes access removal from Jira-managed projects.
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.

cwe · medium confidence lookup

CWE-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-41311 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-41311Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 ServerunspecifiedListed
AtlassianJira Data CenterunspecifiedListed
Weakness

CWE details

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

CWE-287 · source CWE mapping

Improper Authentication

Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.