dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 12 Nov 2025.
Lanscope Endpoint ManagerApplication · Motex

CVE-2025-61932

CRITICAL · 9.8 CVSS v3.0 Published 2025-10-20
Fix available
A fix is available. Upgrade to 9.3.2.7 / 9.3.3.9 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Lanscope Endpoint Manager fails to validate the origin of incoming requests in both its Client program (MR) and Detection agent (DA) components. Attackers can send specially crafted packets that bypass authentication controls, enabling arbitrary code execution on affected systems.

MitigationRestrict network access to management interfaces, implement proper request origin verification (CSRF tokens, proper authentication), and apply vendor patches when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Lanscope Endpoint ManagerApplication
Affected:< 9.3.2.7>= 9.3.3.0, < 9.3.3.9>= 9.4.0.0, < 9.4.0.5>= 9.4.1.0, < 9.4.1.5>= 9.4.2.0, < 9.4.2.6>= 9.4.3.0, < 9.4.3.8>= 9.4.4.0, < 9.4.4.6>= 9.4.5.0, < 9.4.5.4>= 9.4.6.0, < 9.4.6.3>= 9.4.7.0, <= 9.4.7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Lanscope Endpoint Manager version
    Locate the version information for the Motex Lanscope Endpoint Manager installation. This is typically found in the application UI under Help > About, or in the Windows Programs and Features list, or by checking the executable properties of the client program (MR) or Detection agent (DA).
    Affected if The installed version falls into any of these ranges: < 9.3.2.7; >= 9.3.3.0 and < 9.3.3.9; >= 9.4.0.0 and < 9.4.0.5; >= 9.4.1.0 and < 9.4.1.5; >= 9.4.2.0 and < 9.4.2.6; >= 9.4.3.0 and < 9.4.3.8; >= 9.4.4.0 and < 9.4.4.6; >= 9.4.5.0 and < 9.4.5.4; >= 9.4.6.0 and < 9.4.6.3; >= 9.4.7.0 and <= 9.4.7.1
  2. Confirm the client program (MR) or Detection agent (DA) is installed
    Verify that either the Lanscope Endpoint Manager client program (MR) or the Detection agent (DA) is present on the system. Check installed programs list or running processes for Motex Lanscope Endpoint Manager components.
    Affected if Either the MR client program or DA Detection agent is installed and the version is in the affected ranges listed above.
  3. Check network exposure of management interfaces
    Review firewall rules and network configuration to determine if the Lanscope Endpoint Manager service ports are accessible from untrusted networks. The service typically listens on specific ports for client communications.
    Affected if The Lanscope Endpoint Manager service is reachable from network segments that contain untrusted or internet-facing systems, combined with an affected version.

You are affected if Lanscope Endpoint Manager (client program MR or Detection agent DA) is installed and its version falls within any of the vulnerable version ranges listed, and the service is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.3.2.7 / 9.3.3.9 / 9.4.0.5 or later
Fixed in 9.3.2.79.3.3.99.4.0.5
Interim mitigation

Restrict network access to management interfaces, implement proper request origin verification (CSRF tokens, proper authentication), and apply vendor patches when available.

Recommended fix High confidence

9.3.2.7, 9.3.3.9, 9.4.0.5, or 9.4.1.5 (depending on your current version branch)

  1. 1. Identify the current installed version of Lanscope Endpoint Manager by checking the About or Version information within the application or system documentation.
  2. 2. Determine which version branch your current installation belongs to (9.3.x, 9.4.0.x, or 9.4.1.x).
  3. 3. For installations < 9.3.2.7: Upgrade to version 9.3.2.7 or later.
  4. 4. For installations >= 9.3.3.0 and < 9.3.3.9: Upgrade to version 9.3.3.9 or later.
  5. 5. For installations >= 9.4.0.0 and < 9.4.0.5: Upgrade to version 9.4.0.5 or later.
  6. 6. For installations >= 9.4.1.0 and < 9.4.1.5: Upgrade to version 9.4.1.5 or later.
  7. 7. Obtain the upgrade package from the official vendor (MOTEX) at www.motex.co.jp or through your authorized distribution channel.
  8. 8. Before upgrading, backup the current configuration and data according to vendor backup procedures.
Caveat Review vendor release notes for your specific version path for any configuration changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lanscope Endpoint Manager Exploited in the wild — priority engagement
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61932 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data