# CVE-2009-2260: Information disclosure in n/a

> Stardict sends clipboard data to a remote server when Net Dict is enabled, allowing attackers to sniff sensitive information.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 30 Jun 2009
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2009-2260, GHSA-58g7-f54v-2jg8

## What is CVE-2009-2260?

CVE-2009-2260 is a medium-severity vulnerability in n/a, published on 30 Jun 2009. 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

stardict 3.0.1, when Enable Net Dict is configured, sends the contents of the clipboard to a dictionary server, which allows remote attackers to obtain sensitive information by sniffing the network.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2009-2260?

It affects 1 product.


Products: Stardict Stardict.

## How do I fix CVE-2009-2260?

Upgrade to a fixed version.

## Is CVE-2009-2260 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2260 and fix it if it is affected.

What it is: CVE-2009-2260 is a medium-severity vulnerability in n/a, published on 30 Jun 2009. 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-2009-2260 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-2009-2260/ (Markdown: https://insights.sbomify.com/CVE-2009-2260/index.md)
```

## Sources

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

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