/

CVE-2026-34723

Severity:

HIGH RISK

(7.5)

Improper Access Control in Zammad Getting Started Endpoint

CVE-2026-34723

Analyzed

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Sensitive Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Zammad exposed its "getting started" endpoint to unauthenticated users, allowing access to sensitive internal entity data even after initial setup was completed.

An attacker who can reach the affected endpoint over the network may obtain configuration and internal information that should only be visible to authenticated or administrative users.

Affected context

This vulnerability occurs in Zammad's web-based helpdesk application when the "getting started" or initial setup endpoint remains accessible after installation is complete.

In affected deployments, the endpoint continues to serve internal entity data without enforcing proper authentication or authorization checks.

The risk is most pronounced when Zammad is exposed to the internet or untrusted networks, as unauthenticated remote users can query this endpoint.

Exploit preconditions

  • Attack surface: Public or internal HTTP(S) interface of the Zammad server
  • Required access: Network connectivity to the Zammad application; no authentication required
  • Trigger point: Direct requests to the "getting started" or setup-related endpoint after system setup has completed
  • Why exploitation is possible: The endpoint does not correctly enforce access control, allowing unauthenticated users to retrieve internal entity data that should be restricted

Why this happens

The underlying issue is a missing or incomplete authorization check on a setup-related endpoint that was assumed to be used only during initial configuration.

Instead of enforcing strict authentication and role-based access after setup completion, the endpoint continued to respond with sensitive internal entity data to any caller.

This aligns with CWE-284: Improper Access Control, where a resource is exposed without adequate checks to confirm the identity and permissions of the requester.

Potential impact

  • Exposure of internal entity data that may include configuration details, structural metadata, or other sensitive information
  • Facilitation of targeted attacks through reconnaissance on the helpdesk environment and its configuration
  • Potential leakage of information that could assist in social engineering or further privilege escalation attempts
  • Increased attack surface if internal identifiers, endpoints, or workflow details are revealed

General mitigation guidance

Effective mitigation focuses on ensuring that all endpoints—especially setup and onboarding flows—are protected by consistent access control mechanisms.

Useful patterns include:

  • Applying authentication and role-based authorization checks to all endpoints that return internal data, not only to "normal" application routes
  • Implementing a clear lifecycle for setup or wizard endpoints so they are disabled or tightly restricted once installation is complete
  • Centralizing access control logic instead of scattering checks across controllers or views, reducing the chance of missed protections
  • Adopting a default-deny approach, where endpoints must explicitly declare the permissions required before returning sensitive information
  • Periodically reviewing public routes and APIs to confirm they expose only the minimum necessary data

How teams detect issues like this

Organizations can identify similar issues through a mix of code-level and runtime checks:

  • Static analysis and code review: Look for controllers or routes associated with setup, onboarding, or diagnostics that omit authentication/authorization middleware or checks
  • Access control audits: Enumerate all unauthenticated endpoints and verify that none return internal or sensitive data beyond what is explicitly intended
  • Security testing: Use black-box testing or automated scanners to crawl the application as an unauthenticated user and flag endpoints that return structured internal data
  • Logging and monitoring: Track access to setup or administrative endpoints and alert on unexpected access patterns, especially from unauthenticated or external sources

Sources

SourceLink
github.comgithub.com/zammad/zammad/security/advisories/GHSA-hcm9-ch62-5727

Frequently asked

questions

Yes. Any remote attacker who can reach the Zammad web interface over the network can attempt to query the exposed endpoint without authentication.

No. The core issue is that the endpoint lacks proper access control, enabling unauthenticated users to retrieve sensitive internal entity data.

Enforce strict authentication and authorization checks on all endpoints that expose internal or configuration data and disable setup or onboarding routes once installation is complete, following a default-deny access control strategy.

Design setup and administrative features with explicit lifecycle and access policies, centralize access control logic, regularly audit unauthenticated endpoints, and incorporate security reviews or automated checks to ensure no sensitive data is returned without proper authorization.

Find out what's already
exploitable in your codebase.