# CVE-2023-42371: Cross-site scripting in n/a

> A remote attacker can execute arbitrary code via a crafted script in the Summernote editor's insert link function.

- **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:** 18 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-q8v8-p787-f2gx

## What is CVE-2023-42371?

CVE-2023-42371 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Sep 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross Site Scripting vulnerability in Summernote Rich Text Editor v.0.8.18 and before allows a remote attacker to execute arbitrary code via a crafted script to the insert link function in the editor component.

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

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

It affects 1 product.


Products: Summernote Rich Text Editor.

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

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

## Is CVE-2023-42371 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42371 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Sep 2023. 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-2023-42371 exists.

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

## Sources

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

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