Zammad up to 6.4.1 Two Factor Authentication client-side enforcement of server-side security
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Zammad up to 6.4.1 and classified as problematic. Affected by this issue is some unknown functionality of the component Two Factor Authentication. Such manipulation leads to client-side enforcement of server-side security. This vulnerability is traded as CVE-2025-32359. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Zammad up to 6.4.1. It has been rated as problematic. Affected by this issue is an unknown code of the component Two Factor Authentication. The manipulation with an unknown input leads to a client-side enforcement of server-side security vulnerability. Using CWE to declare the problem leads to CWE-602. The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In Zammad 6.4.x before 6.4.2, there is client-side enforcement of server-side security. When changing their two factor authentication configuration, users need to re-authenticate with their current password first. However, this change was enforced in Zammad only on the front end level, and not when using the API directly.
The advisory is shared for download at zammad.com. This vulnerability is handled as CVE-2025-32359 since 04/05/2025. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 6.4.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-14714). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.8
CNA Vector (MITRE): 🔍
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: Client-side enforcement of server-side securityCWE: CWE-602
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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: Zammad 6.4.2
Timeline
04/05/2025 🔍04/06/2025 🔍
04/06/2025 🔍
05/26/2025 🔍
Sources
Advisory: zammad.comStatus: Confirmed
CVE: CVE-2025-32359 (🔍)
GCVE (CVE): GCVE-0-2025-32359
GCVE (VulDB): GCVE-100-303524
EUVD: 🔍
Entry
Created: 04/06/2025 07:36Updated: 05/26/2025 23:53
Changes: 04/06/2025 07:36 (62), 05/26/2025 23:53 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.