Security readout for executives and security teams
Plain-English summary
An authenticated Jira user could remove an issue status from a project even without project administration rights. This is an authorization failure that can disrupt project workflows, issue tracking, and operational reporting, but the provided sources do not indicate code execution, data theft, or active exploitation.
Executive priority
Treat this as a moderate workflow integrity risk. Prioritize remediation for Jira environments supporting regulated, customer-facing, or business-critical projects where unauthorized workflow changes could delay operations or damage reporting reliability.
Technical view
CVE-2019-15013 affects Atlassian Jira before 7.13.12, 8.0.0 before 8.4.3, and 8.5.0 before 8.5.2. The WorkflowResource removeStatus method lacked an authorization check, allowing authenticated remote attackers without project administration access to remove configured issue statuses from projects.
Likely exposure
Exposure is most likely in organizations running affected Jira versions with regular authenticated user access. Internet exposure increases reach, but authentication is still required. The supplied sources do not identify specific deployment types beyond Atlassian Jira.
Exploitation context
The CVE is not listed as KEV in the source bundle, and no cited source states active exploitation. Abuse requires authenticated remote access and targets project workflow status configuration, causing integrity and operational disruption rather than confirmed system compromise.
Researcher notes
Key missing evidence includes CVSS, CWE, exploit maturity, and detailed Atlassian remediation notes beyond fixed version ranges. Avoid assuming broader Atlassian products, unauthenticated exploitation, or active exploitation without additional vendor or KEV evidence.
Mitigation direction
- Upgrade Jira to 7.13.12, 8.4.3, 8.5.2, or later applicable releases.
- Review Atlassian issue JRASERVER-70405 for vendor guidance and affected-version details.
- Restrict Jira access to trusted users until affected instances are upgraded.
- Audit workflow and project status changes for unauthorized removals.
- Back up workflow configuration before remediation or incident review.
Validation and detection
- Inventory Jira versions and compare them with the affected ranges.
- Confirm whether untrusted or broad authenticated user access exists.
- Review project workflows for missing or unexpectedly removed statuses.
- Check audit logs for status-removal events by non-project administrators.
- Verify upgraded instances are outside the affected version ranges.
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-15013 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-70405CVE 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.