A vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the si
A vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the sign-up feature) to perform a full read server-side request forgery via a batch endpoint. This affects Atlassian Jira Server and Data Center from version 8.0.0 before version 8.13.22, from version 8.14.0 before 8.20.10, from version 8.21.0 before 8.22.4. This also affects Jira Management Server and Data Center versions from version 4.0.0 before 4.13.22, from version 4.14.0 before 4.20.10 and from version 4.21.0 before 4.22.4.
- Published
- Jun 30, 2022
- Updated
- Jun 17, 2026
- EPSS
- 71.6% · 99th percentile
- CWE
- CWE-918
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
47
Plan
Add it to your regular patch cycle.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 21 / 30 · 71.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| atlassian | jira data center | cpe:2.3:a:atlassian:jira_data_center |
| atlassian | jira server | cpe:2.3:a:atlassian:jira_server |
| atlassian | jira service desk | cpe:2.3:a:atlassian:jira_service_desk |
| atlassian | jira service management | cpe:2.3:a:atlassian:jira_service_management |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- atlassian jira data center8.0.0 and later · before 8.13.22
- atlassian jira data center8.14.0 and later · before 8.20.10
- atlassian jira data center8.21.0 and later · before 8.22.4
- atlassian jira server8.0.0 and later · before 8.13.22
- atlassian jira server8.14.0 and later · before 8.20.10
- atlassian jira server8.21.0 and later · before 8.22.4
- atlassian jira service desk4.0.0 and later · before 4.13.22
- atlassian jira service management4.14.0 and later · before 4.20.10
- atlassian jira service management4.21.0 and later · before 4.22.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (atlassian). Independent of NVD's CPE analysis and usually ahead of it.
Atlassian Jira Core Server
- 8.0.0 and later · before unspecifiedaffected
- unspecified and later · before 8.13.22affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.20.10affected
- 8.21.0 and later · before unspecifiedaffected
- unspecified and later · before 8.22.4affected
Atlassian Jira Service Management Data Center
- 4.0.0 and later · before unspecifiedaffected
- unspecified and later · before 4.13.22affected
- 4.14.0 and later · before unspecifiedaffected
- unspecified and later · before 4.20.10affected
- 4.21.0 and later · before unspecifiedaffected
- unspecified and later · before 4.22.4affected
Atlassian Jira Service Management Server
- 4.0.0 and later · before unspecifiedaffected
- unspecified and later · before 4.13.22affected
- 4.14.0 and later · before unspecifiedaffected
- unspecified and later · before 4.20.10affected
- 4.21.0 and later · before unspecifiedaffected
- unspecified and later · before 4.22.4affected
Atlassian Jira Software Data Center
- 8.0.0 and later · before unspecifiedaffected
- unspecified and later · before 8.13.22affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.20.10affected
- 8.21.0 and later · before unspecifiedaffected
- unspecified and later · before 8.22.4affected
Atlassian Jira Software Server
- 8.0.0 and later · before unspecifiedaffected
- unspecified and later · before 8.13.22affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.20.10affected
- 8.21.0 and later · before unspecifiedaffected
- unspecified and later · before 8.22.4affected
Same product
atlassian: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26086Affected versions of Atlassian Jira Server and Data Center allow remote attackers to read particular files via a path traversal vulnerabilitKEV81Now
- CVE-2022-0540A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP reques65This week
- CVE-2020-36239Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before 8.13.8, from 8.14.0 b54Plan
- CVE-2022-36801Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to inject arbitrary HTML or JavaScript via a Ref44Plan
- CVE-2020-14179Affected versions of Atlassian Jira Server and Data Center allow remote, unauthenticated attackers to view custom field names and custom SLA44Plan
- CVE-2022-36799This issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.41Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:85 | 2022-06-24 |
| Proof-of-concept repository on GitHub | stars:11 | 2022-07-07 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-6 d
- Published
- TodaySep 29, 2026+1553 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2022-054071 days apartA vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP reques65This week
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- confluence.atlassian.com/display/JIRA/Jira+Server+Security+Advisory+29nd+June+2022
- jira.atlassian.com/browse/JRASERVER-73863
- jira.atlassian.com/browse/JSDSERVER-11840
Vendor advisories and official records. Exploit/PoC links are deliberately left out.