# CVE-2013-1808: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via the id parameter in ZeroClipboard, potentially leading to code execution in the victim's browser.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** Yes
- **Published:** 28 Mar 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-1808, GHSA-rxmh-jwx2-vgrr

## What is CVE-2013-1808?

CVE-2013-1808 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Mar 2013. 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

Cross-site scripting (XSS) vulnerability in ZeroClipboard.swf and ZeroClipboard10.swf in ZeroClipboard before 1.0.8, as used in em-shorty, RepRapCalculator, Fulcrum, Django, aCMS, and other products, allows remote attackers to inject arbitrary web script or HTML via the id parameter.  NOTE: this is might be the same vulnerability as CVE-2013-1463. If so, it is likely that CVE-2013-1463 will be REJECTed.

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

## Which versions are affected by CVE-2013-1808?

It affects 1 product.


Products: Zeroclipboard Project Zeroclipboard.

## How do I fix CVE-2013-1808?

Upgrade to a fixed version.

## Is CVE-2013-1808 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6550](https://insights.sbomify.com/CVE-2012-6550/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1808 and fix it if it is affected.

What it is: CVE-2013-1808 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Mar 2013. 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-2013-1808 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-2013-1808/ (Markdown: https://insights.sbomify.com/CVE-2013-1808/index.md)
```

## Sources

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

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