Security readout for executives and security teams
Plain-English summary
MobaXterm 12.1 can be compromised through a malicious session file. The issue is a memory-safety bug in the username field that may let an attacker run code as the logged-in user. This is most relevant where administrators or engineers exchange MobaXterm session files.
Executive priority
Treat as urgent for teams using MobaXterm 12.1, especially privileged administrators. Prioritize inventory, removal or vendor-guided update, and controls around session-file handling.
Technical view
The bundle describes a CWE-120 SEH-based buffer overflow in Mobatek MobaXterm 12.1 session-file username parsing. Crafted overflow data can trigger arbitrary code execution when the malicious session file is imported and executed. CVSS 3.1 is 9.8, though the description implies target file interaction.
Likely exposure
Exposure is limited to systems running Mobatek MobaXterm 12.1, especially users who import shared, downloaded, or emailed session files. The bundle does not identify other affected versions or platforms.
Exploitation context
The source bundle includes a public ExploitDB entry, so proof-of-concept or exploit details are public. It does not cite CISA KEV listing or evidence of active exploitation in the wild.
Researcher notes
Key evidence is the VulnCheck advisory, CVE record, and ExploitDB reference. The bundle supports arbitrary code execution and public exploit availability, but not active exploitation, affected-version expansion, or a named patch.
Mitigation direction
- Inventory endpoints for Mobatek MobaXterm 12.1.
- Check Mobatek guidance for fixed versions or vendor-recommended remediation.
- Remove or replace affected 12.1 installations where feasible.
- Do not import MobaXterm session files from untrusted sources.
- Restrict sharing of session files through email and file shares.
- Monitor endpoint alerts around MobaXterm launching unexpected child processes.
Validation and detection
- Confirm installed MobaXterm versions across managed endpoints.
- Review whether users import or exchange MobaXterm session files.
- Check security tooling for suspicious MobaXterm process behavior.
- Verify vendor advisory status before declaring remediation complete.
- Document compensating controls if immediate replacement is not possible.
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.
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-25741 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-47429CVE reference, VulnCheck · exploit
- Product ReferenceCVE reference, VulnCheck · product
- VulnCheck Advisory: Mobatek MobaXterm 12.1 Buffer Overflow via Sessions FileCVE reference, VulnCheck · third-party-advisory
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.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.