ZoneMinder up to 1.36.62 Token Authentication web/includes/auth.php validateToken user information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 2.88 |
Summary
A vulnerability marked as problematic has been reported in ZoneMinder up to 1.36.62. Affected by this vulnerability is the function validateToken of the file web/includes/auth.php of the component Token Authentication. The manipulation of the argument User leads to information disclosure.
This vulnerability is listed as CVE-2026-104198. The attack may be initiated remotely. There is no available exploit.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in ZoneMinder up to 1.36.62. It has been rated as problematic. This issue affects the function validateToken of the file web/includes/auth.php of the component Token Authentication. The manipulation of the argument user with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-104198 since 10/01/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
By approaching the search of inurl:web/includes/auth.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.36.63 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 1.36.0
- 1.36.1
- 1.36.2
- 1.36.3
- 1.36.4
- 1.36.5
- 1.36.6
- 1.36.7
- 1.36.8
- 1.36.9
- 1.36.10
- 1.36.11
- 1.36.12
- 1.36.13
- 1.36.14
- 1.36.15
- 1.36.16
- 1.36.17
- 1.36.18
- 1.36.19
- 1.36.20
- 1.36.21
- 1.36.22
- 1.36.23
- 1.36.24
- 1.36.25
- 1.36.26
- 1.36.27
- 1.36.28
- 1.36.29
- 1.36.30
- 1.36.31
- 1.36.32
- 1.36.33
- 1.36.34
- 1.36.35
- 1.36.36
- 1.36.37
- 1.36.38
- 1.36.39
- 1.36.40
- 1.36.41
- 1.36.42
- 1.36.43
- 1.36.44
- 1.36.45
- 1.36.46
- 1.36.47
- 1.36.48
- 1.36.49
- 1.36.50
- 1.36.51
- 1.36.52
- 1.36.53
- 1.36.54
- 1.36.55
- 1.36.56
- 1.36.57
- 1.36.58
- 1.36.59
- 1.36.60
- 1.36.61
- 1.36.62
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: ZoneMinder 1.36.63
Timeline
10/01/2026 CVE reserved10/15/2026 Advisory disclosed
10/15/2026 VulDB entry created
10/15/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-104198 (🔒)
GCVE (CVE): GCVE-0-2026-104198
GCVE (VulDB): GCVE-100-420893
Entry
Created: 10/15/2026 22:17Changes: 10/15/2026 22:17 (67)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.