Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege Nexterm user
-
ExploitObtain another user's session ID
-
ExecutionCall hibernate/resume/DELETE lifecycle endpoint
-
ImpactDisrupt victim's live SSH/RDP/VNC/SFTP session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires an authenticated low-privilege Nexterm account (PR:L) AND possession of another user's valid session ID; with those, the attacker invokes the session lifecycle routes in server/routes/serverSession.js - GET /:id (hibernate), POST /:id/resume, and the DELETE connection endpoint - which, before the fix, did not call validateSessionOwnership(). The primary limiting factors are the need for valid authentication and the need to obtain or guess a target session ID; the impact is confined to disrupting other users' in-progress SSH, RDP, VNC, or SFTP sessions, with no read access to their data. Affected: Nexterm through 1.2.2-BETA; the only complete fix is upgrading to the patched version that enforces ownership validation. |
| Impact | This is a genuine but moderate-severity issue, best characterized as an authorization/IDOR flaw (CWE-639) rather than a critical one. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L) tells a consistent story: network-reachable and low-complexity, but requiring an authenticated low-privilege account (PR:L) and yielding only low integrity and availability impact with no confidentiality loss (VC:N). The score of 5.3 is congruent with the described effect - disruption of other users' live sessions, not data theft or code execution. No EPSS probability, CISA KEV entry, or SSVC automatable/technical-impact data was supplied, and the references contain an issue, a fix PR, and the vulnerable-line pointer but no exploit code, so there is no public exploit identified at time of analysis. The vendor-aligned priority label is 'this_month', which is consistent with a non-emergency authenticated denial/disruption bug. The one caveat worth verifying: the description states the attacker must 'obtain a session ID', which the CVSS vector treats as no added attack requirement (AT:N/AC:L) - if session IDs are not easily enumerable or discoverable, real-world exploitability is lower than the network vector alone implies. Overall this is a legitimate fix-in-normal-cycle item, not a drop-everything priority. |
| Exploit ScenarioDerived | A low-privilege but authenticated Nexterm user obtains another user's active session ID and sends a request to the hibernate, resume, or DELETE connection endpoint under /server-session routes. Because the lifecycle handlers did not verify session ownership, the call succeeds against the victim's session, abruptly hibernating or tearing down their live SSH, RDP, VNC, or SFTP connection. No public exploit code was identified in the provided sources, though the patch diff publicly reveals the exact vulnerable handlers. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 31, 2026
Nexterm through 1.2.2-BETA fails to verify session ownership on its session lifecycle routes, letting any authenticated user hibernate, resume, or terminate another user's live SSH, RDP, VNC, or SFTP session if they know or obtain the target session ID. This is an authorization/IDOR flaw (CWE-639) rated moderate severity: it requires a valid low-privilege account plus a target session identifier, and the outcome is limited to disruption of in-progress sessions with no read access to the victim's data. No public exploit code has been confirmed at time of analysis, and the vendor has addressed the issue in a patched release that enforces ownership validation.
RemediationAI
Upgrade Nexterm to a release containing the ownership-validation fix, delivered via pull request 1950 and commit 00fdb03eea35adb3dee8169469e897b3c8f30657, which add validateSessionOwnership(accountId, sessionId) to hibernateSession, resumeSession and deleteSession; confirm the installed build includes that commit, since the advisory covers all versions through 1.2.2-BETA and no separate patched version number is stated in the available sources. Until the upgrade is applied, the exposure is bounded by two prerequisites: the attacker must hold a valid Nexterm account and must obtain another user's session ID, so restrict account provisioning to trusted operators and review any place session identifiers are logged, shared, or exposed in URLs. Note that no configuration toggle or workaround is documented for disabling the affected routes, so the vendor patched release is the only complete fix per the available evidence; additional upstream context is in issue #1944 and the VulnCheck advisory at https://www.vulncheck.com/advisories/nexterm-through-1.2.2-beta-missing-authorization-in-server-session-lifecycle-routes.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Nexterm is a self-hosted web-based remote connection manager that brokers SSH, RDP, VNC, and SFTP sessions. Its backend (server/routes/serverSession.js, with logic in server/controllers/serverSession.js) exposes session lifecycle endpoints - GET /:id for hibernate, POST /:id/resume, and a DELETE connection route - which invoked hibernateSession(), resumeSession() and deleteSession() using only the session ID taken from the request path. The controller functions had no account-scoping check, so ownership was never compared against the authenticated requester (req.user.id). The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), a classic insecure direct object reference: the session key is user-supplied and the server acted on it without an access-control decision. The upstream fix (pull request 1950, commit 00fdb03) threads accountId into all three controller calls and introduces validateSessionOwnership(accountId, sessionId), returning an error before any hibernate, resume, or delete action is performed. Because the flaw lives in the session control plane rather than the transport layer, it affects all supported connection protocols equally.
Know when Nexterm gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
Authenticated low-privilege account required (PR:L) over the network (AV:N); disrupting others' session state gives limited integrity and availability impact and no confidentiality loss.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Nexterm through 1.2.2-BETA contains a missing authorization vulnerability that allows authenticated users to hibernate, resume, or terminate other users' remote sessions via session lifecycle routes. Attackers who obtain a session ID can call the hibernate, resume, or DELETE connection endpoints to disrupt live SSH, RDP, VNC, or SFTP sessions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
EUVD-2026-114721
GHSA-qprx-3355-vjrx
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB