# CVE-2012-2985: Cross-site scripting in n/a

> Authenticated users can inject arbitrary web script or HTML via the UploadID parameter in Cute Editor, potentially compromising user sessions.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/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:** 21 Aug 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6w88-5pfg-98pf

## What is CVE-2012-2985?

CVE-2012-2985 is a low-severity cross-site scripting vulnerability in n/a, published on 21 Aug 2012. 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 (XSS) vulnerability in InsertDocument.aspx in CuteSoft Cute Editor 6.4 allows remote authenticated users to inject arbitrary web script or HTML via the _UploadID parameter.

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

## Which versions are affected by CVE-2012-2985?

It affects 1 product.


Products: Cutesoft Components Cute Editor.

## How do I fix CVE-2012-2985?

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

## Is CVE-2012-2985 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2985 and fix it if it is affected.

What it is: CVE-2012-2985 is a low-severity cross-site scripting vulnerability in n/a, published on 21 Aug 2012. 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-2012-2985 in the wild and no public exploit code.

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

## Sources

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

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