CVE-2026-104198: ZoneMinder failed token handling bypasses web authentication
ZoneMinder is a free, open source closed-circuit television software application. In versions 1.34.0 through 1.36.38, the web interface mishandles failed token authentication in web/includes/auth.php. validateToken() returns false when a token is malformed or has an invalid signature, but the caller assigns that value to the global $user variable; because web/index.php tests isset($user), boolean false is treated as a present user and the normal login redirect is skipped. This can dispatch views that rely on the outer authentication gate, including the zones view, which accepts an attacker-selected monitor ID and discloses monitor and zone metadata without an independent permission check. Permission helpers receive the false user value and deny privileged operations, so unauthorized state changes have not been established. This vulnerability is fixed in version 1.36.63, where conversion to ZM\User objects causes invalid token state to fail before view dispatch. Later defense-in-depth changes explicitly leave $user unset after failed token validation and reject non-ZM\User values at the web authentication gate.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ZoneMinderto a version that resolves this vulnerability.Fixed in 1.36.63
Event History
Frequently Asked Questions
Which deployments are exposed?
ZoneMinder versions 1.34.0 through 1.36.38 are affected. The issue is reachable through the web interface and can be exploited remotely without authentication.
What does an attacker need to exploit the issue?
An attacker needs to submit a malformed token or a token with an invalid signature to trigger the failed-token path. No valid account, privileges, or user interaction are required.
What information can be exposed?
An attacker can reach views protected only by the outer authentication gate, including the zones view. By selecting a monitor ID, they can disclose monitor and zone metadata.
Are unauthorized configuration changes possible?
Unauthorized state changes have not been established. Permission helpers receive the false user value and deny privileged operations.
What is the remediation?
Upgrade to ZoneMinder 1.36.63, which prevents invalid token state from reaching view dispatch. Later changes also explicitly unset the user after failed token validation and reject non-ZM User values at the web authentication gate.