# CVE-2025-23039: Cross Site Scripting on URL decode Tooltip in Caido

> An attacker can execute arbitrary scripts via the URL decoding tooltip in Caido, potentially stealing sensitive information.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jan 2025
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-3mfw-fhfp-mgrv

## What is CVE-2025-23039?

CVE-2025-23039 is a medium-severity cross-site scripting vulnerability in caido, published on 17 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Caido is a web security auditing toolkit. A Cross-Site Scripting (XSS) vulnerability was identified in Caido v0.45.0 due to improper sanitization in the URL decoding tooltip of HTTP request and response editors. This issue could allow an attacker to execute arbitrary scripts, potentially leading to the theft of sensitive information. This issue has been addressed in version 0.45.1 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

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

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


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

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

## Is CVE-2025-23039 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23039 is a medium-severity cross-site scripting vulnerability in caido, published on 17 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-23039 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-23039/ (Markdown: https://insights.sbomify.com/CVE-2025-23039/index.md)
```

## Sources

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

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