CVE-2025-58386
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 · uneditedIn Terminalfour 8 through 8.4.1.1, the userLevel parameter in the user management function is not subject to proper server-side authorization checks. A Power User can intercept and modify this parameter to assign the Administrator role to other existing lower-privileged accounts, or invite a new lower-privileged account and escalate its privileges. While manipulating this request, the Power User can also change the target account's password, effectively taking full control of it.
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 · high confidenceTerminalfour 8 through 8.4.1.1 has a privilege escalation vulnerability in the user management function. The userLevel parameter lacks server-side authorization validation, allowing a Power User to intercept requests and modify this parameter to assign Administrator roles to existing lower-privileged accounts or newly invited accounts. Additionally, the attacker can change the target account's password during this process, enabling full account takeover.
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>= 8.0.0, < 8.4.1.2CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Terminalfour versionCheck the application version through the admin interface (typically in System Administration > System Info or footer of admin pages), or check the version file in the installation directory if accessibleAffected if Installed version is >= 8.0.0 and < 8.4.1.2
-
Review user role assignments for unauthorized Administrator privilegesIn the admin interface, navigate to System Administration > User Management and export or review the list of all users. Verify that only intended administrators have the Administrator userLevel. Look for accounts that were recently elevated to Administrator statusAffected if Any user account has Administrator privileges that was not assigned that role by an existing Administrator, or there are unexpected Administrator accounts
-
Audit recent user account modificationsCheck system logs or audit logs for user management events, specifically looking for password changes on other user accounts and role modifications performed by Power User accountsAffected if Password changes or role modifications were performed on accounts by users who should not have Administrator-level permissions
-
Identify Power User accounts in the systemIn User Management, filter or list users with Power User role. These accounts have the privilege level required to exploit this vulnerability if server-side authorization is missingAffected if There are Power User accounts present in the system (the vulnerability allows Power Users to escalate privileges)
-
Verify administrator-only restrictions on user management APIsIf you have access to application server logs or can inspect network traffic, check if user management endpoints (POST/PUT requests to user management functions) are being called with Power User credentials while modifying userLevel parameters or other users' passwordsAffected if API calls to modify user roles or passwords are being made without Administrator-level authorization checks
You are affected if your Terminalfour version is between 8.0.0 and 8.4.1.2 inclusive, and you have Power User accounts that could potentially escalate to Administrator privileges through modified userLevel parameters in user management requests.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.4.1.2
Implement proper server-side authorization checks to validate that the requesting user has permission to modify userLevel and perform password changes. Enforce role-based access control (RBAC) on all user management operations.
8.4.1.2
- 1. Identify current Terminalfour version by logging into the admin interface or checking system documentation
- 2. Schedule a maintenance window for the upgrade process
- 3. Perform a complete backup of the Terminalfour database and application files
- 4. Follow the official Terminalfour upgrade documentation to upgrade to version 8.4.1.2 or later
- 5. After upgrade, verify the installation was successful by checking the version number
- 6. Create a test scenario: as a Power User, attempt to modify the userLevel parameter to Administrator role on another account - this should now be blocked
- 7. Confirm existing Administrator accounts can still manage user roles correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58386 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58386 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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