CVE-2026-130853 json
Nexterm through 1.2.2-BETA Privilege Escalation via Permission Group Membership
published 15h ago modified 14h ago also EUVD-2026-127249
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Nexterm through 1.2.2-BETA contains a privilege escalation vulnerability that allows users with permissions.manage to gain unauthorized permissions because addGroupMember and setUserGroups lack the grantsBeyondCaller check. Attackers can add their own account to custom groups via the group membership endpoints to inherit permissions like users.impersonate and settings.backup.
Patch / fix
Is CVE-2026-130853 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.6 | CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 8.6 | CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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 |
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- gnmyt Nexterm
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/gnmyt/Nexterm/commit/9491ece151498a50c3eb1412054dd8362f99ba1a
patch
-
github.com
/gnmyt/Nexterm/issues/2001
issue-tracking
-
github.com
/gnmyt/Nexterm/blob/v1.2.2-BETA/server/controllers/permission.js#L148-L210
technical-description
-
vulncheck.com
/advisories/nexterm-through-1.2.2-beta-privilege-escalation-via-permission-group-membership
third-party-advisory
Sources
- CVE List CVE-2026-130853
- NVD CVE-2026-130853
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.