CVE-2025-61932
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability involves sending specially crafted packets to the client program and detection agent, which is not described as HTTP traffic. Therefore, a web application firewall cannot filter these non-HTTP network packets.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-61932 being exploited?
Yes. CVE-2025-61932 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-61932?
CVE-2025-61932 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-61932?
Yes. A fix has been recorded for CVE-2025-61932. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-61932 affect?
CVE-2025-61932 affects motex:lanscope_endpoint_manager. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affectedVer.9.4.7.1 and earlier
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 22 Oct 2025 (SSVC 2.0.3).
timeline
- 20 Oct 2025Published
- 22 Oct 2025Added to CISA KEV (exploited in the wild) · 2 days later
- 22 Oct 2025CISA SSVC assessment: exploitation active · same day later
- 12 Nov 2025CISA remediation due date (US federal agencies) · 21 days later
- 26 Feb 2026CVE record last updated · 107 days (about 4 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Linkmotex.co.jp /news/notice/2025/release251020/
- Linkjvn.jp /en/jp/JVN86318557/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-61932
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.