dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-69517

HIGH · 8.8 CVSS v3.1 Published 2026-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

HTML injection (stored XSS) vulnerability in Tactical RMM allows authenticated users to inject arbitrary HTML via the agent_id parameter in POST /api/v3/newagent/. The DOMPurify sanitization is configured with html:true, which fails to block dangerous HTML. The payload executes when administrators view or attempt to manage the compromised agent.

MitigationDisable the html:true option in DOMPurify configuration or implement stricter allowlist-based input validation for the agent_id parameter to prevent HTML injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Tactical RMM is installed
    Check for running processes named 'tacticalrmm' or look for the installation directory (commonly /opt/tacticalrmm or /var/www/tacticalrmm). Use 'ps aux | grep -i tactical' or inspect service files.
    Affected if Tactical RMM software is present on the system
  2. Determine Tactical RMM version
    Run 'tacticalrmm -v' or check the version file in the installation directory, typically found in the API's package.json or version.py.
    Affected if Installed version matches or falls within the affected range (verify against official advisory)
  3. Locate DOMPurify configuration
    Search the codebase for 'DOMPurify' configuration files. Common paths include the API source directory under /api/ or /rmmapi/, look for files containing 'dompurify' or 'sanitize'. Use 'grep -r "html.*true" --include="*.js" .' in the project directory.
    Affected if DOMPurify is configured with html:true option enabled
  4. Verify the vulnerable API endpoint exists
    Check if the file handling POST /api/v3/newagent/ exists in the API routing configuration. Look for routes.py or urls.py files defining the newagent endpoint.
    Affected if The /api/v3/newagent/ endpoint is exposed and accessible
  5. Inspect stored agent_id values for injection payloads
    Query the database for agent records with unusual agent_id values containing HTML tags (<script>, <img>, <iframe>, event handlers like onload/onerror). Use: SELECT agent_id FROM agents WHERE agent_id LIKE '%<%';
    Affected if Any agent records contain HTML or script tags in the agent_id field

A user is affected if Tactical RMM is running, the installed version is within the affected range, DOMPurify has html:true enabled, and malicious agent_id values exist in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the html:true option in DOMPurify configuration or implement stricter allowlist-based input validation for the agent_id parameter to prevent HTML injection.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69517 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data