# CVE-2019-1010113: Cross-site scripting in CLEditor

> An attacker can inject arbitrary HTML and script code into websites using the CLEditor jQuery plugin via crafted link attributes.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 19 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hh56-x62g-gvhc

## What is CVE-2019-1010113?

CVE-2019-1010113 is a medium-severity cross-site scripting vulnerability in Premium Software CLEditor, published on 19 Jul 2019. 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

Premium Software CLEditor 1.4.5 and earlier is affected by: Cross Site Scripting (XSS). The impact is: An attacker might be able to inject arbitrary html and script code into the web site. The component is: jQuery plug-in. The attack vector is: the victim must open a crafted href attribute of a link (A) element.

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

## Which versions are affected by CVE-2019-1010113?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `CLEditor` | NuGet | All versions to 1.4.5 | None |
| `CLEditor` | NuGet | All versions to 1.4.5 | None |

Products: Premiumsoftware Cleditor.

## How do I fix CVE-2019-1010113?

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

## Is CVE-2019-1010113 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1010113 and fix it if it is affected.

What it is: CVE-2019-1010113 is a medium-severity cross-site scripting vulnerability in Premium Software CLEditor, published on 19 Jul 2019. 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-2019-1010113 in the wild and no public exploit code.

Affected packages and fixed versions:
- CLEditor (NuGet): affected all versions up to 1.4.5; no fix listed
- CLEditor (NuGet): affected all versions up to 1.4.5; 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-2019-1010113/ (Markdown: https://insights.sbomify.com/CVE-2019-1010113/index.md)
```

## Sources

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

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