Security readout for executives and security teams
Plain-English summary
This Jira Server and Data Center flaw could let an anonymous remote user keep seeing cached content after their permissions were removed. The main risk is unintended disclosure of Jira content, not system takeover or data modification.
Executive priority
Prioritize remediation for internet-facing or anonymously accessible Jira instances because the issue can expose sensitive project content without login. It is high priority for confidentiality, but sources do not indicate active exploitation.
Technical view
CVE-2021-39113 is a broken access control issue in Jira's allowlist feature. Affected versions are before 8.13.9 and 8.14.0 through before 8.18.0. CVSS 3.1 is 7.5, driven by network reachability, no authentication requirement, and high confidentiality impact.
Likely exposure
Organizations running Atlassian Jira Server or Jira Data Center in the affected version ranges are potentially exposed, especially where Jira is internet-accessible or anonymous access is enabled.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector indicates anonymous network exploitation is possible, but only confidentiality impact is identified.
Researcher notes
Evidence is limited to the CVE description and Atlassian issue reference. The weakness is tagged CWE-613, and the described behavior is stale cached access after permission loss through the allowlist feature.
Mitigation direction
- Upgrade Jira Server or Data Center to 8.13.9, 8.18.0, or a later non-affected release.
- Review Atlassian issue JRASERVER-72573 for vendor guidance and affected-version details.
- Audit anonymous access and allowlist-related configuration on Jira instances.
- Treat exposed Jira content as potentially disclosed until affected instances are remediated.
Validation and detection
- Inventory Jira Server and Data Center versions across all environments.
- Confirm no production instance runs before 8.13.9 or 8.14.0 through before 8.18.0.
- Review whether anonymous users can reach Jira content or cached content paths.
- After remediation, verify permission removal prevents continued cached-content visibility.
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.
CWE-613: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2021-39113 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
- 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:H/I:N/A:N
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 vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/JRASERVER-72573CVE 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.
Insufficient Session Expiration
Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.