dbcve.org
Privileged Remote AccessApplication · Beyondtrust

CVE-2025-5309

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-16
Fix available
A fix is available. Upgrade to 24.3.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The chat feature within Remote Support (RS) and Privileged Remote Access (PRA) is vulnerable to a Server-Side Template Injection vulnerability which can lead to remote code execution.

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

Server-Side Template Injection (SSTI) vulnerability in the chat feature of Remote Support (RS) and Privileged Remote Access (PRA) allows attackers to inject malicious template code through chat input, which is then rendered by the server-side template engine, leading to arbitrary code execution.

MitigationDisable or restrict the chat feature until a vendor patch is available; implement input validation and output encoding for all user-supplied data in template contexts.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Privileged Remote AccessApplication
Affected:>= 24.2.2, <= 24.2.4>= 24.3.1, < 24.3.4= 25.1.1
Remote SupportApplication
Affected:>= 24.2.2, <= 24.2.4>= 24.3.1, < 24.3.4= 25.1.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed product and version
    Locate the BeyondTrust software installation and check the version number displayed in the product interface (typically found in the Help > About section) or check the installation directory for version metadata files.
    Affected if The installed version falls within these ranges: 24.2.2 through 24.2.4, 24.3.1 through 24.3.3, or exactly 25.1.1.
  2. Confirm the product type
    Determine whether the installation is BeyondTrust Privileged Remote Access (PRA) or BeyondTrust Remote Support (RS), as both products share this vulnerability.
    Affected if The product is either BeyondTrust Privileged Remote Access or BeyondTrust Remote Support.
  3. Verify the chat feature is in use
    Check if the chat/chatting functionality is enabled in the product configuration. This is typically found in the administrative settings under session configuration or customer/attendee settings.
    Affected if The chat feature is enabled and available for use in the current deployment.
  4. Review chat-related access and activity logs
    Examine server logs, session logs, or chat transcript records for any unusual template syntax patterns (such as {{ }}, ${ }, {% %}, or other templating delimiters) appearing in chat message content.
    Affected if Chat logs contain unexpected characters or syntax patterns typical of template injection attempts.

A user is affected if they have BeyondTrust Remote Support or Privileged Remote Access installed with a version in the affected ranges AND the chat feature is enabled.

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.

dbcve · scoped
Upgrade available Upgrade to 24.3.4 or later
Fixed in 24.3.4
Interim mitigation

Disable or restrict the chat feature until a vendor patch is available; implement input validation and output encoding for all user-supplied data in template contexts.

Recommended fix Moderate confidence

PRA/RS 24.3.5 or later, or PRA/RS 25.1.2 or later (depending on your current branch)

  1. 1. Identify the currently installed version of BeyondTrust Privileged Remote Access (PRA) or Remote Support (RS) by accessing the product administrative interface or checking system information.
  2. 2. Based on your current version, determine the appropriate upgrade path: if running 24.2.x, upgrade to 24.3.5 or later; if running 24.3.x (24.3.1-24.3.4), upgrade to 24.3.5 or later; if running 25.1.1, upgrade to 25.1.2 or later.
  3. 3. Obtain the upgrade package from the official BeyondTrust support portal at www.beyondtrust.com or through your authorized BeyondTrust representative.
  4. 4. Before applying the upgrade, perform a complete backup of the system configuration and database as recommended by BeyondTrust documentation.
  5. 5. Apply the upgrade following BeyondTrust's standard upgrade procedures documented in the product administration guide.
  6. 6. After upgrade completion, verify the chat feature functionality and confirm the system is operational.
  7. 7. Validate that the running version matches the expected fixed version (24.3.5+ or 25.1.2+).
Caveat Review BeyondTrust release notes for your specific upgrade path for any configuration or compatibility changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Privileged Remote Access Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5309 — 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-5309 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