# CVE-2025-55014: Information disclosure in StarDict

> The YouDao plugin for StarDict transmits user data to remote servers via cleartext HTTP, allowing attackers to intercept sensitive information.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:** 4 Aug 2025
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-55014, GHSA-mr85-g3h9-44r6, MGASA-2025-0298, UBUNTU-CVE-2025-55014

## What is CVE-2025-55014?

CVE-2025-55014 is a medium-severity vulnerability in StarDict, published on 4 Aug 2025. 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

The YouDao plugin for StarDict, as used in stardict 3.0.7+git20220909+dfsg-6 in Debian trixie and elsewhere, sends an X11 selection to the dict.youdao.com and dict.cn servers via cleartext HTTP.

Weakness: CWE-402 (Transmission of Private Resources into a New Sphere)

## Which versions are affected by CVE-2025-55014?


## How do I fix CVE-2025-55014?

Upgrade to a fixed version.

## Is CVE-2025-55014 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55014 and fix it if it is affected.

What it is: CVE-2025-55014 is a medium-severity vulnerability in StarDict, published on 4 Aug 2025. 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-2025-55014 in the wild and no public exploit code.

Affected product: StarDict. 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-2025-55014/ (Markdown: https://insights.sbomify.com/CVE-2025-55014/index.md)
```

## Sources

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

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