VulnerabilityPublished 31 Oct 2024Updated 1 Nov 2024

CVE-2024-48200

Source CVE Database V5

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

8.4High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-48200, organizations should immediately restrict local access to systems running MobaXterm 24.2, ensuring only trusted users have physical or remote desktop access. Monitor and audit usage of MobaXterm and MSI installer operations for unusual activity, especially processes spawning conhost.exe with elevated privileges. Until an official patch is released, consider uninstalling MobaXterm or reverting to a previous, unaffected version if feasible. Employ application whitelisting and endpoint detection and response (EDR) solutions to detect and block unauthorized privilege escalation attempts. Harden Windows security policies by enforcing least privilege principles and disabling unnecessary local administrator accounts. Additionally, educate users about the risks of local privilege escalation and enforce strict access controls on shared systems. Regularly check for updates from MobaXterm vendors and apply patches promptly once available. Implementing these targeted controls will reduce the attack surface and limit the potential for exploitation.

Description

An issue in MobaXterm v24.2 allows a local attacker to escalate privileges and execute arbitrary code via the remove function of the MobaXterm MSI is spawning one Administrative cmd (conhost.exe)

Impact

The impact of CVE-2024-48200 is significant as it allows local attackers to gain administrative privileges on affected Windows systems running MobaXterm 24.2. This privilege escalation can lead to complete system compromise, enabling attackers to install malware, steal sensitive data, modify system configurations, or disrupt system availability. Organizations relying on MobaXterm for remote management or development tasks face increased risk, especially if endpoint security is weak or local access controls are insufficient. The vulnerability undermines the confidentiality, integrity, and availability of affected systems. In environments with shared or multi-user access, the risk of lateral movement and further exploitation increases. Although exploitation requires local access, the ease of exploitation without user interaction or authentication amplifies the threat. This vulnerability could be leveraged in targeted attacks or insider threat scenarios, impacting sectors such as finance, government, healthcare, and critical infrastructure where MobaXterm usage is prevalent.

References

Community reviews

Loading reviews…