dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-34024

HIGH · 8.6 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 →
92/100
Remediation priority · Urgent
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 missing authorization checks on multiple web application endpoints. An authenticated attacker with minimal privileges can access endpoints that are not visible in the frontend but remain directly reachable. This allows the attacker to perform restricted actions such as switching the user's branch, uploading arbitrary files, downloading arbitrary files, and viewing details of arbitrary branches.

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 web application has missing authorization checks on multiple API endpoints. Authenticated users with minimal privileges can directly access hidden endpoints not exposed in the frontend UI, enabling them to perform privileged actions including switching branches, uploading/downloading arbitrary files, and viewing details of arbitrary branches.

MitigationImplement proper authorization validation on all API endpoints, enforce role-based access control (RBAC) for each action, and ensure backend permission checks occur regardless of whether endpoints are linked in the frontend.

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:H/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. Confirm Wertheim SafeController Software installation
    Locate the software installation directory or check system services for Wertheim SafeController components. Look for application binaries, configuration files, or running processes associated with the product.
    Affected if The software is present and running in the environment
  2. Identify if web interface or API is enabled
    Check configuration files (typically in conf/ or config/ directories) for web server settings, API enable flags, or service port configurations. Look for HTTP/HTTPS listeners or REST API settings.
    Affected if Web interface or API endpoints are enabled and accessible
  3. Review endpoint authorization configuration
    Examine application configuration or access control policy files to identify which endpoints exist and whether they have explicit authorization checks defined. Look for ACL, permission, or role configuration sections.
    Affected if Endpoints lack defined authorization rules or have misconfigured access controls
  4. Check for hidden or privileged endpoint exposure
    Review API routing configuration, URL mappings, or endpoint definitions to identify all available paths. Compare against documented public endpoints to find undocumented or hidden routes.
    Affected if Hidden or administrative endpoints exist without proper authorization enforcement
  5. Verify user role and privilege assignment
    Inspect user account configurations, role definitions, and permission mappings. Determine if low-privilege users can be assigned to roles that grant access to sensitive operations like branch switching, file upload/download, or branch detail viewing.
    Affected if Low-privilege authenticated users can access privileged actions or unauthorized data

The environment is affected if the Wertheim SafeController Software is running with its web/API interface enabled and lacks proper authorization enforcement on sensitive endpoints, allowing minimal-privilege users to perform privileged actions.

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 authorization validation on all API endpoints, enforce role-based access control (RBAC) for each action, and ensure backend permission checks occur regardless of whether endpoints are linked in the frontend.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34024 — 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-34024 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