WpdiscuzWordPress extension · Gvectors
CVE-2026-22192
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 · uneditedVoltronic Power SNMP Web Pro version 1.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to access privileged management functions by manipulating browser localStorage values. Attackers can modify client-side authentication state to bypass server-side access controls and gain unauthorized access to protected management functionality without valid credentials.
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 confidenceVoltronic Power SNMP Web Pro 1.1 incorrectly trusts client-side localStorage values to determine authentication state, allowing attackers to modify these values to bypass server-side access controls and gain unauthorized access to privileged management functions without valid credentials.
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
WpdiscuzWordPress extension
< 7.6.47CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L
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.
-
Verify Wpdiscuz plugin versionCheck the installed Wpdiscuz version through WordPress admin plugin list, or inspect the plugin header in wpdiscuz.php file in wp-content/plugins/wpdiscuz/Affected if Installed version is below 7.6.47
-
Inspect browser localStorage usageOpen the site in a browser, open developer tools (F12), go to Application tab, expand Local Storage section, and look for any keys related to user sessions, authentication, or user rolesAffected if Application stores session tokens, user IDs, roles, or authentication flags in localStorage
-
Check for client-side role checksReview JavaScript source files in the plugin for code that reads localStorage values and makes access control decisions based on those values without server validationAffected if JavaScript code uses localStorage.getItem() to retrieve user role or auth state and grants access to features based solely on those client-side values
-
Test unauthenticated access to management endpointsUsing browser developer tools or a request tool, attempt to access typical admin/management URLs while not logged in, then modify localStorage to set authentication-related keys (like isLoggedIn, userRole:admin) and retry those requestsAffected if Privileged functions become accessible after setting localStorage values without any server-side session validation
User is affected if running Wpdiscuz below version 7.6.47 AND the application relies on localStorage values for authentication decisions without server-side validation.
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 data7.6.47
Replace client-side authentication state reliance with robust server-side session validation and implement proper authentication checks on all privileged endpoints; conduct thorough testing to ensure all access control paths are enforced server-side.
Fix this in Wpdiscuz
Scoped from the published advisory
- Consultation6.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22192 — 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-2026-22192 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