# CVE-2022-24799: Cross Site Scripting in Wire Webapp > Insufficient escaping in Wire webapp markdown allows attackers to inject JavaScript via malicious messages, leading to full account takeover. - **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something - **Fix available:** No - **Published:** 20 Apr 2022 - **Updated:** 23 Apr 2025 - **Also known as:** GHSA-5568-rfh8-vmhq ## What is CVE-2022-24799? CVE-2022-24799 is a critical cross-site scripting vulnerability in wireapp wire-webapp, published on 20 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description wire-webapp is the web application interface for the wire messaging service. Insufficient escaping in markdown “code highlighting” in the wire-webapp resulted in the possibility of injecting and executing arbitrary HTML code and thus also JavaScript. If a user receives and views such a malicious message, arbitrary code is injected and executed in the context of the victim. This allows the attacker to fully control the user account. Wire-desktop clients that are connected to a vulnerable wire-webapp version are also vulnerable to this attack. The issue has been fixed in wire-webapp 2022-03-30-production.0 and is already deployed on all Wire managed services. On-premise instances of wire-webapp need to be updated to docker tag 2022-03-30-production.0-v0.29.2-0-d144552 or wire-server 2022-03-30 (chart/4.8.0), so that their applications are no longer affected. There are no known workarounds for this issue. ### Patches * The issue has been fixed in wire-webapp **2022-03-30-production.0** and is already deployed on all Wire managed services. * On-premise instances of wire-webapp need to be updated to docker tag **2022-03-30-production.0-v0.29.2-0-d144552** or wire-server **2022-03-30 (chart/4.8.0)**, so that their applications are no longer affected. ### Workarounds * No workarounds known ### For more information If you have any questions or comments about this advisory feel free to email us at [vulnerability-report@wire.com](mailto:vulnerability-report@wire.com) ### Credits We thank [Posix](https://twitter.com/po6ix) for reporting this vulnerability Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2022-24799? It affects 1 product. Products: Wire Wire-Webapp. ## How do I fix CVE-2022-24799? No fix has been published for CVE-2022-24799 yet. Limit exposure of the affected software until one is available. ## Is CVE-2022-24799 being exploited? There is no known exploitation of CVE-2022-24799 in the wild and no public exploit code. ## Other vulnerabilities in wireapp wire-webapp - [CVE-2022-29168](https://insights.sbomify.com/CVE-2022-29168/): Cross Site Scripting in Wire Messages (critical 9.6) - [CVE-2021-32683](https://insights.sbomify.com/CVE-2021-32683/): XSS through createObjectURL (high 8.8) - [CVE-2021-21400](https://insights.sbomify.com/CVE-2021-21400/): Entering code in App Lock modal sends input to conversation (high 7.1) - [CVE-2025-48066](https://insights.sbomify.com/CVE-2025-48066/): wire-webapp has no database deletion on client logout (medium 6.0) - [CVE-2022-39380](https://insights.sbomify.com/CVE-2022-39380/): wire-webapp contains Improper Handling of Exceptional Conditions leading to a DoS via Markdown Rendering (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-24799 and fix it if it is affected. What it is: CVE-2022-24799 is a critical cross-site scripting vulnerability in wireapp wire-webapp, published on 20 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-24799 in the wild and no public exploit code. Affected product: wireapp wire-webapp. 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-2022-24799/ (Markdown: https://insights.sbomify.com/CVE-2022-24799/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24799 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24799 - OSV: https://osv.dev/vulnerability/CVE-2022-24799 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-24799/ Summaries are generated and may contain mistakes; the official description above is the record.