Security readout for executives and security teams
Plain-English summary
A critical flaw in MOTEX's on-premises Lanscope Endpoint Manager lets an unauthenticated attacker run their own code on machines running the Client (MR) or Detection Agent (DA) software. Because the bug is being exploited in the wild and listed by CISA, organizations using affected versions should treat patching as an emergency.
Executive priority
Treat as emergency patch. CISA KEV listing means attackers are actively exploiting this on internet-exposed Lanscope deployments; schedule remediation within standard KEV deadlines.
Technical view
CVE-2025-61932 is an improper origin verification flaw (CWE-940) in the Lanscope Endpoint Manager on-premises Client (MR) and Detection Agent (DA) at Ver.9.4.7.1 and earlier. A remote, unauthenticated attacker can send specially crafted packets to the agent and achieve arbitrary code execution. CVSS v3.0 base score 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Likely exposure
Any organization running on-premises Lanscope Endpoint Manager Client (MR) or Detection Agent (DA) at version 9.4.7.1 or earlier is exposed. Risk is highest where the agent's network port is reachable from untrusted segments or the internet, but lateral exploitation from compromised internal hosts is also plausible.
Exploitation context
Listed in CISA's Known Exploited Vulnerabilities catalog, indicating confirmed in-the-wild exploitation. The CVSS 9.8 vector (network, no privileges, no user interaction) means an attacker who can reach the agent's listening port can trigger arbitrary code execution by sending crafted packets.
Researcher notes
Root cause is improper origin validation of incoming requests (CWE-940) on the MR/DA components, allowing arbitrary code execution via crafted packets. CVSS 9.8 with AV:N/AC:L/PR:N/UI:N suggests the listener accepts unauthenticated traffic from any reachable source. Affected scope is Ver.9.4.7.1 and earlier; consult the MOTEX advisory and JVN entry for the fixed build and any compensating controls. KEV status confirms active exploitation; hunt for anomalous processes, outbound connections, or persistence created under the Lanscope agent service account.
Mitigation direction
- Inventory all Lanscope MR and DA agents and identify versions at or below 9.4.7.1.
- Apply the fixed version per MOTEX advisory as the priority remediation path.
- Until patched, restrict network access to agent ports via host and network firewalls.
- Isolate or take offline any internet-exposed Lanscope management or agent endpoints.
- Monitor for unexpected child processes spawned by the Lanscope agent service.
- Follow the CISA KEV remediation deadline for federal-style governance.
Validation and detection
- Query asset inventory for Lanscope MR/DA installs and capture installed version strings.
- Cross-reference results against the fixed version called out in the MOTEX advisory.
- Verify CISA KEV listing and any internal SLA tied to KEV deadlines.
- Scan internal and perimeter networks for hosts exposing Lanscope agent listener ports.
- Review EDR and process logs for anomalous activity by the Lanscope agent process.
- Confirm post-patch version on a sample of endpoints before closing the ticket.
Public sources used
Michael Williams reviewed this cited source version on .
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-940: 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-2025-61932 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.0)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.0/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.
CISA KEV status
CVSS vector scores
1 official scoreWe 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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
9.8CriticalVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.motex.co.jp/news/notice/2025/release251020/CVE reference
- https://jvn.jp/en/jp/JVN86318557/CVE reference
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-61932CVE reference · government-resource
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.
Improper Verification of Source of a Communication Channel
Improper Verification of Source of a Communication Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.