CVE-2025-32359
MEDIUMDescription
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.
Is your site exposed to CVE-2025-32359?
Run a free security scan — no signup, results in seconds.
CVSS v3.1 Score
Weakness Type (CWE)
Affected Products
| Vendor | Product |
|---|---|
| zammad | zammad |
References
Advisories & Patches
Frequently Asked Questions
What is CVE-2025-32359? +
How severe is CVE-2025-32359? +
What products are affected by CVE-2025-32359? +
How do I check if I'm vulnerable to CVE-2025-32359? +
Related Vulnerabilities
The Vitogate 300 web interface fails to enforce proper server-side authentication and relies on frontend-based authentication controls. This allows an …
Data Space Portal is an open-source Software as a Service (SaaS) solution designed to streamline Dataspace management. From version 2.1.1 …
This vulnerability exists in Meon KYC solutions due to insufficient server-side validation of the Captcha in certain API endpoints. A …
In Quick.CMS, the administrative user interface restricts deletion of the primary language by omitting the corresponding option from the interface; …
In JetBrains IntelliJ IDEA before 2026.2 unauthorized settings modification was possible in a Remote Development session
A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.5), RUGGEDCOM ROX MX5000RE (All versions < V2.16.5), …