Security readout for executives and security teams
Plain-English summary
This Jira flaw lets a remote attacker abuse a logged-in user's browser to create new Jira resolution values. It is not described as data theft or code execution, but it can corrupt workflow data, reporting, and ticket lifecycle controls.
Executive priority
Treat this as a targeted integrity risk for Jira operations. Prioritize remediation for externally reachable or business-critical Jira instances, but it is not currently evidenced as exploited in the provided sources.
Technical view
CVE-2019-11586 is a CSRF issue in Jira AddResolution.jspa. Affected versions are before 7.13.6, 8.0.0 before 8.2.3, and 8.3.0 before 8.3.2. The source data provides no CVSS score or CWE.
Likely exposure
Organizations running affected Jira versions are exposed, especially where administrators or privileged users access Jira through browsers and can be targeted with CSRF.
Exploitation context
The bundle does not cite active exploitation, and CISA KEV status is false. Exploitation is described only as remote CSRF-based creation of Jira resolutions.
Researcher notes
Evidence is limited to the CVE description and Atlassian issue reference. No CVSS, CWE, exploit status, or detailed workaround is provided in the bundle, so avoid assuming impact beyond CSRF creation of resolutions.
Mitigation direction
- Upgrade affected Jira versions to 7.13.6, 8.2.3, 8.3.2, or a later supported release.
- Review Atlassian issue JRASERVER-69783 for vendor-specific guidance and fixed-version confirmation.
- Restrict Jira administrative access to trusted users while remediation is pending.
- Educate Jira administrators to avoid untrusted links while logged in until patched.
Validation and detection
- Inventory all Jira instances and record exact versions.
- Compare deployed versions against the affected ranges in the CVE description.
- Check Jira configuration for unexpected or unauthorized resolution values.
- Confirm remediation by verifying the installed version is at or beyond the fixed range.
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-2019-11586 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-69783CVE 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.