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

> Authenticated users can inject HTML into agent IDs, leading to UI manipulation or phishing in the management panel.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2026
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-hf64-2g6g-cxvv

## What is CVE-2025-69517?

CVE-2025-69517 is a high-severity cross-site scripting vulnerability in n/a, published on 28 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An HTML injection vulnerability in Amidaware Inc Tactical RMM v1.3.1 and earlier allows authenticated users to inject arbitrary HTML content during the creation of a new agent via the POST /api/v3/newagent/ endpoint. The agent_id parameter accepts up to 255 characters and is improperly sanitized using DOMPurify.sanitize() with the html: true option enabled, which fails to adequately filter HTML input. The injected HTML is rendered in the Tactical RMM management panel when an administrator attempts to remove or shut down the affected agent, potentially leading to client-side attacks such as UI manipulation or phishing. NOTE: the Supplier's position is that this has incorrect information.

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

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


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

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

## Is CVE-2025-69517 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69517 is a high-severity cross-site scripting vulnerability in n/a, published on 28 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-69517 in the wild and no public exploit code.

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

## Sources

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

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