# CVE-2022-23461: Cross-Site Scripting (XSS) in Jodit Editor

> Attackers can execute arbitrary scripts via specially constructed input pasted into the Jodit Editor, affecting applications using this library.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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:** 24 Sep 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-42hx-vrxx-5r6v

## What is CVE-2022-23461?

CVE-2022-23461 is a medium-severity cross-site scripting vulnerability in xdan Jodit Editor, published on 24 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Jodit Editor is a WYSIWYG editor written in pure TypeScript without the use of additional libraries. Jodit Editor is vulnerable to XSS attacks when pasting specially constructed input. This issue has not been fully patched. There are no known workarounds.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-23461?

2 open source packages ship an affected version, including jodit. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jodit` | npm | All versions to 3.24.2 | None |
| `jodit` | npm | All versions to 3.24.2 | None |

Products: Xdsoft Jodit Editor.

## How do I fix CVE-2022-23461?

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

## Is CVE-2022-23461 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23461 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23461 and fix it if it is affected.

What it is: CVE-2022-23461 is a medium-severity cross-site scripting vulnerability in xdan Jodit Editor, published on 24 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23461 exists.

Affected packages and fixed versions:
- jodit (npm): affected all versions up to 3.24.2; no fix listed
- jodit (npm): affected all versions up to 3.24.2; no fix listed

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-23461/ (Markdown: https://insights.sbomify.com/CVE-2022-23461/index.md)
```

## Sources

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

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