# CVE-2025-54374: Eidos: One-click Remote Code Execution through Custom URL Handling

> Attackers can achieve remote code execution by tricking users into visiting a website with a malicious custom URL scheme.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 3 Oct 2025
- **Updated:** 3 Oct 2025
- **Also known as:** GHSA-qhhm-56qp-xr2r

## What is CVE-2025-54374?

CVE-2025-54374 is a high-severity code injection vulnerability in mayneyao eidos, published on 3 Oct 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

Eidos is an extensible framework for Personal Data Management. Versions 0.21.0 and below contain a one-click remote code execution vulnerability. An attacker can exploit this vulnerability by embedding a specially crafted eidos: URL on any website, including a malicious one they control. When a victim visits such a site or clicks on the link, the browser triggers the app’s custom URL handler (eidos:), causing the Eidos application to launch and process the URL, leading to remote code execution on the victim’s machine. This issue does not have a fix as of October 3, 2025

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Mayneyao Eidos.

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

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

## Is CVE-2025-54374 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54374 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54374 is a high-severity code injection vulnerability in mayneyao eidos, published on 3 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54374 exists.

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

## Sources

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

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