Security readout for executives and security teams
Plain-English summary
MobaXterm 11.1 can be abused through its custom mobaxterm: link handler. If a user opens a malicious link, an attacker may cause commands to run on that user’s workstation. This is most relevant to phishing, drive-by links, and environments where MobaXterm is installed on administrator or developer machines.
Executive priority
Prioritize remediation on administrator and developer workstations. The business risk is workstation compromise from a link-click scenario, especially where MobaXterm is used for privileged access. The limited source data warrants verification before broad emergency action.
Technical view
The mobaxterm: URI handler in MobaXterm 11.1 has an argument injection flaw. A remote attacker can pass unintended command-line arguments through a crafted URL and reach command execution behavior exposed by the application. The provided bundle does not include CVSS, CWE, fixed-version, or vendor mitigation details.
Likely exposure
Exposure is likely limited to endpoints with MobaXterm 11.1 installed and the mobaxterm: URI protocol handler registered. Risk is higher for privileged users, administrators, developers, and systems where browsers or email clients can launch custom protocol links.
Exploitation context
The source bundle supports remote command execution after user interaction with a specially crafted URL. It does not show CISA KEV listing or other evidence of active exploitation. Treat exploitation status as unconfirmed, not known exploited.
Researcher notes
Affected metadata in the bundle is incomplete and lists vendor/product as n/a, but the description specifically names MobaXterm 11.1. No public CVSS, CWE, patch level, or KEV evidence is provided. Avoid assuming other versions are affected without vendor confirmation.
Mitigation direction
- Inventory endpoints for MobaXterm 11.1 installations.
- Check vendor guidance for fixed versions or recommended configuration changes.
- Upgrade affected installations if a vendor-supported fixed release is available.
- Disable or restrict the mobaxterm: URI handler where business workflows allow.
- Harden browsers and email clients against unsolicited custom protocol launches.
Validation and detection
- Confirm whether MobaXterm 11.1 is installed on managed endpoints.
- Verify whether the mobaxterm: protocol handler is registered.
- Identify users with administrative privileges who run affected installations.
- Review endpoint telemetry for unexpected MobaXterm launches from browsers or mail clients.
- Confirm remediation by rechecking version and protocol-handler state.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-13475 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.vulnerability-lab.com/get_content.php?id=2186CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
