Security readout for executives and security teams
Plain-English summary
This issue affects certain Atlassian Jira Server and Data Center versions. A remote anonymous attacker could use a CSRF flaw to turn Jira Software configuration features on or off. The public bundle does not provide CVSS scoring or evidence of active exploitation.
Executive priority
Schedule remediation in the normal vulnerability cycle, escalating for internet-facing or business-critical Jira systems. The risk is meaningful because configuration can be changed without authorization, but source evidence does not support emergency active-exploitation handling.
Technical view
CVE-2021-26071 is a CSRF vulnerability in SetFeatureEnabled.jspa in Jira Server and Data Center before 8.5.13, 8.6.0 before 8.13.5, and 8.14.0 before 8.15.1. The described impact is unauthorized enabling or disabling of Jira Software configuration.
Likely exposure
Exposure is likely limited to organizations running affected Jira Server or Data Center versions. Internet-facing Jira instances increase business concern, but the bundle does not confirm exploit prerequisites beyond remote anonymous CSRF.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV in the bundle. Treat exploitation status as unconfirmed, not absent.
Researcher notes
Evidence is sparse: no CVSS vector, CWE, exploit proof, or detailed prerequisites are included in the bundle. Analysis should stay anchored to the affected version ranges and the stated SetFeatureEnabled.jspa CSRF behavior.
Mitigation direction
- Upgrade affected Jira Server or Data Center instances to a fixed version or later.
- Use 8.5.13, 8.13.5, or 8.15.1 as applicable version baselines.
- Review Atlassian JRASERVER-72233 for vendor remediation guidance.
- Prioritize externally reachable Jira instances during remediation planning.
Validation and detection
- Inventory Jira Server and Data Center versions across all environments.
- Check whether versions fall below the fixed release thresholds.
- Review Jira configuration change history for unexpected feature toggles.
- Confirm Atlassian advisory status for any updated remediation instructions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2021-26071 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/JRASERVER-72233CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.