# CVE-2021-41313: Missing authorization in Jira Data Center

> Authenticated non-admin users can modify email batch configurations in Atlassian Jira Server and Data Center due to improper authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2021
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-5pjh-5gpx-359v

## What is CVE-2021-41313?

CVE-2021-41313 is a medium-severity missing authorization vulnerability in Atlassian Jira Data Center, published on 1 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Affected versions of Atlassian Jira Server and Data Center allow authenticated but non-admin remote attackers to edit email batch configurations via an Improper Authorization vulnerability in the /secure/admin/ConfigureBatching!default.jspa endpoint. The affected versions are before version 8.20.7.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2021-41313?

It affects 2 products.


Products: Atlassian Jira Data Center, Atlassian Jira Server.

## How do I fix CVE-2021-41313?

No fix has been published for CVE-2021-41313 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41313 being exploited?

There is no known exploitation of CVE-2021-41313 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Jira Data Center

- [CVE-2021-26086](https://insights.sbomify.com/CVE-2021-26086/): Atlassian Jira Server and Data Center Path Traversal (medium 5.3, exploited in the wild)
- [CVE-2022-0540](https://insights.sbomify.com/CVE-2022-0540/): Auth bypass in Jira Core Server (critical 9.8)
- [CVE-2020-36239](https://insights.sbomify.com/CVE-2020-36239/): Deserialization in Jira Core Data Center (critical 9.8)
- [CVE-2025-22167](https://insights.sbomify.com/CVE-2025-22167/): Path traversal in Jira Software Data Center (high 8.7)
- [CVE-2019-20419](https://insights.sbomify.com/CVE-2019-20419/): Other in Jira Server (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41313 and fix it if it is affected.

What it is: CVE-2021-41313 is a medium-severity missing authorization vulnerability in Atlassian Jira Data Center, published on 1 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41313 in the wild and no public exploit code.

Affected product: Atlassian Jira Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-41313/ (Markdown: https://insights.sbomify.com/CVE-2021-41313/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-41313
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-41313
- OSV: https://osv.dev/vulnerability/CVE-2021-41313

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-41313/
Summaries are generated and may contain mistakes; the official description above is the record.