Threats / BeyondTrust / CVE-2024-12356
CVE-2024-12356
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
BeyondTrust Privileged Remote Access (PRA) and Support (RS) vulnerability
BeyondTrust Privileged Remote Access and Remote Support contain an unauthenticated command injection vulnerability allowing attackers to execute arbitrary commands with site user privileges.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can inject and execute arbitrary commands through a command injection flaw in BeyondTrust PRA and RS, potentially compromising privileged access infrastructure and connected systems.
CISA KEV Yes · 2024-12-195EPSS 0.87991 (verify live)6CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4Exploit Weaponized · public exploit · Metasploit module13
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-12-19).
Probability (EPSS)
EPSS 0.87991 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: BeyondTrust, Privileged Remote Access (PRA) and Remote Support (RS) . Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-77 Command Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify the vulnerable endpoint in BeyondTrust PRA or RS that accepts unsanitized command input without authentication.
Business
The organization's privileged access management layer becomes directly exposed to external attack without credential requirements.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft and inject malicious commands into the vulnerable parameter, exploiting the lack of input validation.
Business
Attackers gain execution context as a site user, potentially escalating to administrative or system-level privileges.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute commands to establish persistence, exfiltrate credentials, or pivot to downstream systems managed by the PAM solution.
Business
The compromise of privileged access infrastructure enables lateral movement across the entire enterprise infrastructure and credential theft.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05