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.
Metrics
Affected Vendors & Products
References
Link | Providers |
---|---|
https://zammad.com/en/advisories/zaa-2025-02 |
![]() ![]() |
History
Tue, 15 Apr 2025 16:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Zammad
Zammad zammad |
|
Weaknesses | NVD-CWE-Other | |
CPEs | cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:* | |
Vendors & Products |
Zammad
Zammad zammad |
Sat, 05 Apr 2025 21:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-602 | |
Metrics |
cvssV3_1
|
Sat, 05 Apr 2025 21:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
References |
|

Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2025-04-07T16:12:34.420Z
Reserved: 2025-04-05T00:00:00.000Z
Link: CVE-2025-32359

No data.

Status : Analyzed
Published: 2025-04-05T21:15:40.657
Modified: 2025-04-15T15:31:20.960
Link: CVE-2025-32359

No data.