# CVE-2025-65270: Cross-site scripting in n/a

> Unauthenticated attackers can execute arbitrary JavaScript in victim browsers via reflected XSS in ClinCapture EDC, potentially leading to session hijacking or data theft.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 22 Dec 2025
- **Updated:** 23 Dec 2025
- **Also known as:** GHSA-jj84-f8gw-6c9j

## What is CVE-2025-65270?

CVE-2025-65270 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Dec 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

Reflected cross-site scripting (XSS) vulnerability in ClinCapture EDC 3.0 and 2.2.3, allowing an unauthenticated remote attacker to execute JavaScript code in the context of the victim's browser.

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

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

It affects 1 product.


Products: Clincapture Captivate Electronic Data Capture.

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

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

## Is CVE-2025-65270 being exploited?

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

Public exploit code:

- Reflected XSS in ClinCapture EDC (github_poc): https://github.com/xh4vm/CVE-2025-65270

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65270 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Dec 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-65270 exists.

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

## Sources

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

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