Two-factor configuration tampering via API reauthentication bypass
Published Apr 5, 2025 · Updated Apr 7, 2025
Incorrect access control in Zammad 6.4.x before 6.4.2 allows remote authenticated users to change two-factor settings through the API. The two-factor configuration API accepts the change without verifying the current password because reauthentication was enforced only by the frontend. A valid user session is required, and the bypass permits modification of that account's two-factor authentication configuration.
Summary
What happened
Incorrect access control in Zammad 6.4.x before 6.4.2 allows remote authenticated users to change two-factor settings through the API. The two-factor configuration API accepts the change without verifying the current password because reauthentication was enforced only by the frontend. A valid user session is required, and the bypass permits modification of that account's two-factor authentication configuration.
The record
- CVE
- CVE-2025-32359
- Published
- Apr 5, 2025
- Updated
- Apr 7, 2025
- Vendor
- Zammad
- Product
- Zammad
- Classifications
- CWE-602, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 2025CVE publishedPublication date reported by the CVE source.
- Apr 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.4 <6.4.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo