# CVE-2025-53834: Caido Toast Vulnerable to Reflected Cross-site Scripting


- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Jul 2025
- **Updated:** 15 Jul 2025
- **Also known as:** GHSA-h8jr-c6qq-h7m7

## What is CVE-2025-53834?

CVE-2025-53834 is a medium-severity vulnerability in caido, published on 14 Jul 2025. 

### Official description

Caido is a web security auditing toolkit. A reflected cross-site scripting (XSS) vulnerability was discovered in Caido’s toast UI component in versions prior to 0.49.0. Toast messages may reflect unsanitized user input in certain tools such as Match&Replace and Scope. This could allow an attacker to craft input that results in arbitrary script execution. Version 0.49.0 fixes the issue.

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

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


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

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

## Is CVE-2025-53834 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53834 is a medium-severity vulnerability in caido, published on 14 Jul 2025. 
Exploitation: There is no known exploitation of CVE-2025-53834 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-53834/ (Markdown: https://insights.sbomify.com/CVE-2025-53834/index.md)
```

## Sources

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

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