# CVE-2025-66025: Caido Improperly Handles External Links in Markdown

> Attackers can inject malicious links into Caido findings, redirecting users to attacker-controlled domains for phishing attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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:** No
- **Published:** 26 Nov 2025
- **Updated:** 26 Nov 2025
- **Also known as:** GHSA-cf52-h5mw-gmc2

## What is CVE-2025-66025?

CVE-2025-66025 is a medium-severity vulnerability in caido, published on 26 Nov 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

Caido is a web security auditing toolkit. Prior to version 0.53.0, the Markdown renderer used in Caido’s Findings page improperly handled user-supplied Markdown, allowing attacker-controlled links to be rendered without confirmation. When a user opened a finding generated through the scanner, or other plugins, clicking these injected links could redirect the Caido application to an attacker-controlled domain, enabling phishing style attacks. This issue has been patched in version 0.53.0.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2025-66025 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66025 is a medium-severity vulnerability in caido, published on 26 Nov 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-66025 in the wild and no public exploit code.

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

## Sources

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

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