/

CVE-2026-22192

Severity:

CRITICAL RISK

(9.9)

Missing Authentication in Voltronic Power SNMP Web Pro

CVE-2026-22192

Modified

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Authentication Bypass Leading to Unauthorized Administrative Access

Severity:

CRITICAL RISK

(9.9)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Voltronic Power SNMP Web Pro 1.1 contains an authentication bypass flaw where client-side authentication state stored in browser localStorage is trusted to gate privileged management functions.

By manipulating these localStorage values, an unauthenticated attacker can bypass server-side access controls and gain unauthorized access to protected management functionality without valid credentials.

Affected context

This vulnerability affects deployments of Voltronic Power SNMP Web Pro 1.1 where the web-based management interface relies on client-side state (such as values stored in browser localStorage) to determine whether a user is authenticated or has administrative privileges.

The issue is present when the server does not robustly re-validate credentials or enforce authorization on each request and instead trusts flags or tokens controlled by the browser to allow access to sensitive management endpoints.

Exploit preconditions

  • Attack surface: Public or internal web interface exposed by the Voltronic Power SNMP Web Pro management console.
  • Required access: Network access to the web interface; no valid credentials required.
  • Trigger point: Any HTTP request to privileged management functions where access control is inferred from client-controlled localStorage values.
  • Why exploitation is possible: The server-side logic implicitly trusts client-side authentication indicators (e.g., a localStorage flag or token) instead of enforcing authentication and authorization checks on the server for each privileged action.

Why this happens

The core issue is a missing server-side enforcement of authentication and authorization for privileged management operations, aligning with CWE-306: Missing Authentication for Critical Function.

Instead of deriving access decisions solely on the server from verified session data or credentials, the application relies on mutable client-side state stored in localStorage to represent whether a user is logged in or has elevated privileges.

Because localStorage is entirely under the control of the user agent, an attacker can simply modify these values to set themselves as "authenticated" or "admin," and the server fails to perform independent verification before executing protected functions.

Potential impact

  • Unauthenticated users can gain access to administrative or otherwise privileged management panels.
  • Attackers may modify device or network configuration managed by the SNMP Web Pro interface.
  • Malicious changes can disrupt power management, monitoring, or alerting behavior associated with the product.
  • Unauthorized users may add, alter, or delete accounts and other security-relevant settings.
  • Compromise of the management interface can facilitate broader network reconnaissance or lateral movement.

General mitigation guidance

Effective mitigation focuses on enforcing all authentication and authorization checks on the server side and treating client-side state as untrusted.

Recommended design patterns include:

  • Implementing robust, server-managed session handling (e.g., HTTP-only cookies with secure session IDs) and deriving user identity and role solely from server-side session state.
  • Applying strict access control checks on every request to privileged endpoints, independent of any client-controlled data such as localStorage, query parameters, or hidden form fields.
  • Using a consistent authorization layer that maps authenticated identities to allowed operations, ensuring that critical functions cannot be invoked without proper authentication.
  • Minimizing sensitive logic in front-end code and avoiding client-side indicators as the single source of truth for authentication or privilege status.
  • Applying the principle of least privilege so that the default state of unauthenticated connections is no access to management operations.

How teams detect issues like this

Detection typically combines design review with targeted testing:

  • Code review: Look for authorization decisions based on client-controlled variables (localStorage, sessionStorage, JavaScript variables, URL parameters) rather than server-side session data or access control middleware.
  • Static analysis: Configure rules to flag uses of localStorage or other client storage in authentication flows, or to detect server routes that lack explicit authentication/authorization checks.
  • Dynamic testing: Use a proxy to inspect and replay requests to privileged endpoints with and without valid authentication; verify whether modifying client-side state alone permits access.
  • Security testing policies: Integrate automated tests in CI/CD that assert all sensitive routes pass through authentication middleware or access control components.

Sources

SourceLink
github.comgithub.com/kmkz/Exploits/blob/master/2026/CVE-2026-22192-22199_Voltronic-Power_Preauth_root_RCE.txt
voltronicpower.comvoltronicpower.com/
boffsec-services.comboffsec-services.com/posts/sicuroweb-cve-2026-22191/
vulncheck.comvulncheck.com/advisories/voltronic-power-snmp-web-pro-authentication-bypass-via-localstorage

Frequently asked

questions

Yes. Any attacker with network access to the Voltronic Power SNMP Web Pro web interface can attempt to exploit this issue by manipulating client-side storage, even without possessing valid credentials.

The attacker only needs the ability to reach the web management interface over the network. Local control of a browser is assumed, but no prior authentication or account is required.

Move all authentication and authorization logic to the server side, use server-managed sessions, and require that all privileged operations check the authenticated user and their permissions on the server before executing.

Establish a design rule that client-side state (including localStorage, cookies, and JavaScript variables) is never the sole basis for authentication or authorization decisions, and enforce this via code review, security architecture guidelines, and automated checks that ensure all sensitive endpoints are protected by server-side access control.

Find out what's already
exploitable in your codebase.