# CVE-2023-22522: Code injection in Confluence Data Center

> Authenticated attackers can inject unsafe input into Confluence pages to achieve remote code execution on affected Data Center and Server instances.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2023
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-rcjw-44p8-ppj6

## What is CVE-2023-22522?

CVE-2023-22522 is a critical code injection vulnerability in Atlassian Confluence Data Center, published on 6 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This Template Injection vulnerability allows an authenticated attacker, including one with anonymous access, to inject unsafe user input into a Confluence page. Using this approach, an attacker is able to achieve Remote Code Execution (RCE) on an affected instance. Publicly accessible Confluence Data Center and Server versions as listed below are at risk and require immediate attention. See the advisory for additional details

Atlassian Cloud sites are not affected by this vulnerability. If your Confluence site is accessed via an atlassian.net domain, it is hosted by Atlassian and is not vulnerable to this issue.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2023-22522?

It affects 2 products.


Products: Atlassian Confluence Data Center, Atlassian Confluence Server.

## How do I fix CVE-2023-22522?

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

## Is CVE-2023-22522 being exploited?

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

## Other vulnerabilities in Atlassian Confluence Data Center

- [CVE-2023-22527](https://insights.sbomify.com/CVE-2023-22527/): Atlassian Confluence Data Center and Server Template Injection (critical 10.0, exploited in the wild)
- [CVE-2023-22518](https://insights.sbomify.com/CVE-2023-22518/): Atlassian Confluence Data Center and Server Improper Authorization (critical 10.0, exploited in the wild)
- [CVE-2023-22515](https://insights.sbomify.com/CVE-2023-22515/): Atlassian Confluence Data Center and Server Broken Access Control (critical 10.0, exploited in the wild)
- [CVE-2022-26134](https://insights.sbomify.com/CVE-2022-26134/): Atlassian Confluence Server and Data Center Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2021-26084](https://insights.sbomify.com/CVE-2021-26084/): Atlassian Confluence Server and Data Center Object-Graph Navigation Language (OGNL) Injection (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22522 and fix it if it is affected.

What it is: CVE-2023-22522 is a critical code injection vulnerability in Atlassian Confluence Data Center, published on 6 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22522 in the wild and no public exploit code.

Affected product: Atlassian Confluence 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-2023-22522/ (Markdown: https://insights.sbomify.com/CVE-2023-22522/index.md)
```

## Sources

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

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