CVE-2026-54213: TeamDavid: Denial of Service via endpoint 'internalRestart'
Tobit Laboratories AG TeamDavid's Webbox application exposes a functionality that allows the server to be
shut down when a specific endpoint (/internalRestart) is accessed. This
endpoint is accessible to unauthenticated users over the public
Internet. Instead of “restarting”, the server shuts completely down. As a
result, a remote attacker can trigger a persistent denial of service by
shutting down the web server without requiring authentication. Recovery
requires manual administrator intervention to restart the service. This issue affects TeamDavid before Rollout 528.
Starting with Rollout 528 (June 30, 2026), the affected functionality is disabled by default and the vulnerabilities are therefore no longer exposed through this functionality.
Security readout for executives and security teams
Plain-English summary
An unauthenticated Internet user can shut down a vulnerable TeamDavid Webbox server by reaching an exposed internal function. The service remains unavailable until an administrator manually restarts it, creating substantial operational disruption. TeamDavid releases before Rollout 528 are affected; Rollout 528 disables the functionality by default.
Executive priority
Treat Internet-exposed, pre-Rollout 528 systems as an immediate availability risk. Prioritize upgrading or isolating them because disruption requires no credentials and recovery is manual. Although active exploitation is not documented, the low-complexity remote condition warrants urgent action for business-critical messaging or collaboration services.
Technical view
CVE-2026-54213 is an improper-access-control flaw affecting TeamDavid before Rollout 528. The Webbox application exposes its internalRestart functionality without authentication. Invoking it shuts down the server rather than restarting it, causing persistent denial of service and requiring manual recovery. The supplied CVSS 4.0 score is 9.2, with high vulnerable-system and subsequent-system availability impact.
Likely exposure
Highest risk applies to pre-Rollout 528 TeamDavid Webbox deployments where the affected functionality is Internet-accessible. Internal-only or otherwise restricted deployments may have lower practical exposure, but the supplied sources do not establish which configurations prevent access. Asset owners should confirm rollout level, Webbox deployment, and external reachability.
Exploitation context
The weakness is remotely reachable, requires no authentication or user interaction, and has low stated attack complexity. Successful abuse can repeatedly cause persistent service outages. The supplied record is not in KEV, and no cited source establishes active exploitation in the wild; exploit prevalence is therefore unknown.
Researcher notes
The supplied classification is CWE-284. The primary security effect is persistent denial of service, with the CVSS vector also recording high subsequent-system availability impact. Avoid production endpoint testing because validation could stop the service. The bundle does not provide request details, forensic indicators, affected configuration variants, or evidence of exploitation.
Mitigation direction
Upgrade TeamDavid to Rollout 528 or later.
Confirm the affected functionality remains disabled after upgrading.
Until upgraded, restrict untrusted network access to the Webbox application.
Check Tobit release notes and current vendor guidance for additional safeguards.
Prepare documented manual service-recovery procedures for unexpected shutdowns.
Validation and detection
Inventory TeamDavid Webbox instances and record each rollout level.
Identify instances running releases earlier than Rollout 528.
Verify whether each Webbox instance is reachable from the public Internet.
Confirm the affected functionality is disabled through configuration review, without triggering it.
Review availability monitoring for unexplained shutdowns requiring manual recovery.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.