CVE-2025-36729
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 · uneditedA non-primary administrator user with admin rights to the web interface but without shell access permissions can display configuration of the device including the master admin password. This vulnerability also allows the user to give themselves shell access with the root gid.
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 confidenceA privilege escalation vulnerability in the web interface allows non-primary administrator users with web admin rights but without shell access permissions to view sensitive device configuration including the master admin password, and to self-grant shell access with root gid.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Confirm web interface is enabledAccess the device's web admin portal URL (typically https://<device-ip>/admin or similar). If the login page loads, the web interface is active.Affected if The web interface is accessible and accepts authentication.
-
Identify non-primary administrator accountsLog into the web interface with a non-primary admin account (not the master/admin account). Navigate to User Management or Admin Users settings panel to enumerate accounts with web admin privileges.Affected if Multiple admin accounts exist with web access permissions.
-
Check for sensitive config exposureAs a non-primary admin user, locate the Device Configuration, System Settings, or Backup/Restore section within the web interface. Look for fields displaying the master admin password or other sensitive credentials.Affected if Non-primary admins can view the master admin password or sensitive configuration data through the web UI.
-
Verify privilege escalation vectorsAs a non-primary admin, check for options to modify user permissions, enable SSH/Telnet access, or change account privileges. Look for features that allow granting shell access, modifying user groups, or enabling root-level services.Affected if Non-primary admin accounts can self-grant shell access, modify their own privilege level, or enable root-level services.
-
Review RBAC configurationIn the web interface admin panel, locate Role-Based Access Control or Privilege Settings. Verify whether restrictions are in place to prevent web admins from accessing system-level configuration or escalating privileges.Affected if RBAC is either absent, misconfigured, or fails to restrict web admin users from sensitive operations.
A user is affected if the web interface is accessible and allows non-primary administrator accounts to view sensitive configuration (including master passwords) or to self-grant shell/root-level access privileges.
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.
From vendor dataImplement strict role-based access control (RBAC) in the web interface to prevent non-primary admins from accessing sensitive configuration data and restrict privilege escalation capabilities.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36729 — 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-36729 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