Motex LANSCOPE Endpoint Manager Improper Verification of Source of a Communication Channel
CVE-2025-61932 is a critical-severity improper verification of source of a communication channel vulnerability in Lanscope Endpoint Manager (On-Premises) (Client program (MR) and Detection agent (DA)) from MOTEX, with a CVSS 4.0 base score of 9.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Lanscope Endpoint Manager (On-Premises) (Client program (MR) and Detection agent (DA)) versions: Ver.9.4.7.1 and earlier. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on October 22, 2025, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Lanscope Endpoint Manager to 9.3.2.7 or 9.3.3.9 or 9.4.0.5 or 9.4.1.5, whichever matches your release line, or a later version.
- CISA's required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- Read the advisory on motex.co.jp for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| MOTEX | Lanscope Endpoint Manager (On-Premises) (Client program (MR) and Detection agent (DA)) | Ver.9.4.7.1 and earlier | Not stated |
| Motex | Lanscope Endpoint Manager | before 9.3.2.7; 9.3.3.0 up to, but not including, 9.3.3.9; 9.4.0.0 up to, but not including, 9.4.0.5; 9.4.1.0 up to, but not including, 9.4.1.5; 9.4.2.0 up to, but not including, 9.4.2.6; 9.4.3.0 up to, but not including, 9.4.3.8; 9.4.4.0 up to, but not including, 9.4.4.6; 9.4.5.0 up to, but not including, 9.4.5.4; and 2 more ranges | 9.3.2.7, 9.3.3.9, 9.4.0.5, 9.4.1.5, 9.4.2.6, 9.4.3.8 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- NoneThe attack does not depend on a particular deployment or configuration.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- NoneNo loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- NoneNo loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- NoneNo loss of availability on systems beyond the vulnerable one.
Vector: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA (jpcert.or.jp).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.3 | Critical | CNA (jpcert.or.jp) |
| CVSS 3.0 | 9.8 | Critical | CNA (jpcert.or.jp) |
Official description
Lanscope Endpoint Manager (On-Premises) (Client program (MR) and Detection agent (DA)) improperly verifies the origin of incoming requests, allowing an attacker to execute arbitrary code by sending specially crafted packets.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Verification of Source of a Communication Channel
The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.
How developers prevent this class of flaw
- Use a mechanism that can validate the identity of the source, such as a certificate, and validate the integrity of data to ensure that it cannot be modified in transit using an Adversary-in-the-Middle (AITM) attack. When designing functionality of actions in the URL scheme, consider whether the action should be accessible to all mobile applications, or if an allowlist of applications to interface with is appropriate.
More Improper Verification of Source of a Communication Channel vulnerabilities (CWE-940)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: total).
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- jvn.jp/en/jp/JVN86318557/Third Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-61932Third Party Advisory, US Government Resource
Recent Improper Verification of Source of a Communication Channel vulnerabilities
- 7.6 High severity
- 7.0 High severity
- 8.4 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.