dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39675

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in webmuehle Court Reservation court-reservation allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Court Reservation: from n/a through <= 1.10.11.

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 confidence

Missing authorization vulnerability in webmuehle Court Reservation allows attackers to exploit incorrectly configured access control security levels. The vulnerability enables unauthorized access to reservation functionality due to improper or missing authorization checks on certain endpoints or operations, likely allowing users to access resources or actions beyond their intended privilege level.

MitigationImplement proper authorization checks on all sensitive endpoints and enforce role-based access control (RBAC) to verify user permissions before executing operations.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify if webmuehle Court Reservation system is installed
    Check your application inventory or web server for installations of webmuehle Court Reservation software. Look for directories or services named 'court-reservation', 'webmuehle', or similar. Inspect running web services on common ports (80, 443, 8080) for the application's login or reservation pages.
    Affected if The webmuehle Court Reservation system is present in the environment
  2. Determine the installed version of the reservation system
    Check version information in the application about page, configuration files, or footer of web pages. Common locations: /about, /info, VERSION file in installation directory, or footer of HTML pages. Compare your version against any official release notes from webmuehle.
    Affected if The installed version is older than the patched release (if known) or cannot be determined to be current
  3. Verify authorization on reservation endpoints
    Access reservation-related URLs (such as /reservation, /booking, /court/book, or similar reservation paths) using an account without elevated privileges. Attempt to view, create, modify, or delete reservations that should require elevated permissions. Capture HTTP responses to identify if access is granted without proper role verification.
    Affected if Unauthenticated or low-privilege users can access reservation functions that should require admin or elevated roles
  4. Inspect access control configuration
    Examine the application's configuration files for security level settings. Look for files like config.php, security.xml, roles.yml, or similar in the installation directory. Check for parameters controlling authorization enforcement such as 'security_level', 'access_control', 'require_auth', or role-based access definitions.
    Affected if Security level settings are absent, misconfigured, or set to permissive values (e.g., 'low' or 'disabled')
  5. Test role-based access control enforcement
    Create or use multiple user accounts with different roles (e.g., regular user, admin). For each role, attempt to access reservation functions that should be restricted to higher-privilege roles. Compare the application's behavior against documented role permissions.
    Affected if Lower-privileged users can perform actions reserved for higher-privileged roles, indicating broken access control

A defender is affected if the webmuehle Court Reservation system is present and unauthorized users can access reservation functionality that should require elevated permissions, or if security configuration lacks proper role-based access controls.

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 checks on all sensitive endpoints and enforce role-based access control (RBAC) to verify user permissions before executing operations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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