# CVE-2024-21686: Cross-site scripting in Confluence Data Center > An authenticated attacker can inject malicious scripts into Confluence pages, allowing arbitrary code execution in victims' browsers. - **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 16 Jul 2024 - **Updated:** 19 Mar 2025 - **Also known as:** GHSA-7x4x-g7pr-2356 ## What is CVE-2024-21686? CVE-2024-21686 is a high-severity cross-site scripting vulnerability in Atlassian Confluence Data Center, published on 16 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description This High severity Stored XSS vulnerability was introduced in versions 7.13 of Confluence Data Center and Server. This Stored XSS vulnerability, with a CVSS Score of 7.3, allows an authenticated attacker to execute arbitrary HTML or JavaScript code on a victims browser which has high impact to confidentiality, high impact to integrity, no impact to availability, and requires user interaction. Atlassian recommends that Confluence Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions listed on this CVE See the release notes (https://confluence.atlassian.com/doc/confluence-release-notes-327.html). You can download the latest version of Confluence Data Center and Server from the download center (https://www.atlassian.com/software/confluence/download-archives). This vulnerability was reported via our Bug Bounty program. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-21686? It affects 2 products. Products: Atlassian Confluence Data Center, Atlassian Confluence Server. ## How do I fix CVE-2024-21686? No fix has been published for CVE-2024-21686 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-21686 being exploited? There is no known exploitation of CVE-2024-21686 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-2024-21686 and fix it if it is affected. What it is: CVE-2024-21686 is a high-severity cross-site scripting vulnerability in Atlassian Confluence Data Center, published on 16 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-21686 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-2024-21686/ (Markdown: https://insights.sbomify.com/CVE-2024-21686/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-21686 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-21686 - OSV: https://osv.dev/vulnerability/CVE-2024-21686 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-21686/ Summaries are generated and may contain mistakes; the official description above is the record.