dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-34023

HIGH · 7.1 CVSS v4.0 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
The Wertheim SafeController Software, AssemblyVersion 6.15.8328.28014, contains an incorrect authorization vulnerability in the WebSocket communication used by the SafeController WebMessageBroker. An authenticated attacker with valid low-privileged branch user credentials can manipulate WebSocket messages by specifying controller identifiers belonging to other branches. This allows the attacker to access restricted functions and resources in other branches, including activating boxes outside of the user's authorized branch.

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 confidence

The Wertheim SafeController Software has an incorrect authorization vulnerability in its WebSocket-based WebMessageBroker. Authenticated low-privileged users can manipulate WebSocket messages to specify controller identifiers from other branches, bypassing branch-level access controls and gaining unauthorized access to restricted functions like activating boxes in other branches.

MitigationImplement proper server-side authorization validation in the WebMessageBroker to enforce branch-based access controls, ensuring users can only access controllers and functions within their authenticated branch.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Wertheim SafeController Software version
    Check the application installation directory, About screen, or version registry entry for the SafeController Software. Common locations: C:\Program Files\Wertheim\SafeController\ or /opt/wertheim/safecontroller/
    Affected if Version matches or precedes the vulnerable range (software history shows this vulnerability affects versions prior to fixed release)
  2. Verify WebSocket WebMessageBroker is enabled
    Locate the WebMessageBroker configuration file (typically named WebMessageBroker.config, broker.xml, or similar in the config directory). Check for enabled="true" or a WebSocket listener configuration.
    Affected if WebSocket-based WebMessageBroker is active and listening for connections
  3. Examine branch access control configuration
    Review the access control or authorization configuration files for the WebMessageBroker. Look for branch-based permission settings, typically in auth.xml, security.xml, or branch_config.xml.
    Affected if Branch-level access controls are defined but missing or flawed cross-branch validation logic
  4. Inspect WebSocket message handling for controller identifier validation
    If source code or decompiled binaries are available, examine the WebSocket message handler in the WebMessageBroker component. Search for code that processes controller identifiers without validating branch membership.
    Affected if Code allows controller identifiers from other branches to be specified without proper branch membership verification
  5. Test for cross-branch controller access
    Using an authenticated low-privilege user session, send a WebSocket message to the WebMessageBroker with a controller identifier from a different branch. Observe if the request is accepted or rejected.
    Affected if Requests specifying controllers from other branches are accepted and executed without authorization failure

A user is affected if the WebSocket WebMessageBroker is enabled and lacks proper server-side branch-based authorization validation, allowing cross-branch controller access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper server-side authorization validation in the WebMessageBroker to enforce branch-based access controls, ensuring users can only access controllers and functions within their authenticated branch.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing10.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,660
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34023 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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