How severe is CVE-2025-32359?

CVE-2025-32359 has a CVSS 3.x base score of 4.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.

Is CVE-2025-32359 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-32359?

CVE-2025-32359 affects Zammad. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-32359?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-32359 have an EU (EUVD) identifier?

Yes. CVE-2025-32359 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-14714.

When was CVE-2025-32359 published?

CVE-2025-32359 was published on 2025-04-05 and last updated on 2026-06-17.

CVE-2025-32359

CVE-2025-32359 is a medium-severity vulnerability in Zammad with a CVSS 3.x base score of 4.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-602.

Key facts

Severity: Medium (CVSS 3.x base score 4.8)
EPSS exploit prediction: 0% (19th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-14714
Weakness: CWE-602
Affected product: Zammad
Published: 2025-04-05
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-32359?: 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.
How severe is CVE-2025-32359?: CVE-2025-32359 has a CVSS 3.x base score of 4.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2025-32359 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-32359?: CVE-2025-32359 affects Zammad. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-32359?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-32359 have an EU (EUVD) identifier?: Yes. CVE-2025-32359 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-14714.
When was CVE-2025-32359 published?: CVE-2025-32359 was published on 2025-04-05 and last updated on 2026-06-17.

References

https://zammad.com/en/advisories/zaa-2025-02

Affected products (1)

cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:*

More vulnerabilities in Zammad

CVE-2022-48021 — Critical (CVSS 9.8): A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted…
CVE-2022-35490 — Critical (CVSS 9.8): Zammad 5.2.0 is vulnerable to privilege escalation. Zammad has a prevention against brute-force attacks trying to guess…
CVE-2021-42090 — Critical (CVSS 9.8): An issue was discovered in Zammad before 4.1.1. The Form functionality allows remote code execution because…
CVE-2021-42094 — Critical (CVSS 9.8): An issue was discovered in Zammad before 4.1.1. Command Injection can occur via custom Packages.
CVE-2020-26030 — Critical (CVSS 9.8): An issue was discovered in Zammad before 3.4.1. There is an authentication bypass in the SSO endpoint via a crafted…
CVE-2017-6080 — Critical (CVSS 9.8): An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1, caused by lack of a…

All CVEs affecting Zammad →

Other CWE-602 vulnerabilities

CVE-2026-42160 — Critical (CVSS 10.0): Data Space Portal is an open-source Software as a Service (SaaS) solution designed to streamline Dataspace management.…
CVE-2025-33025 — Critical (CVSS 9.9): A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.5), RUGGEDCOM ROX MX5000RE (All…
CVE-2025-33024 — Critical (CVSS 9.9): A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.5), RUGGEDCOM ROX MX5000RE (All…
CVE-2025-32469 — Critical (CVSS 9.9): A vulnerability has been identified in RUGGEDCOM ROX MX5000 (All versions < V2.16.5), RUGGEDCOM ROX MX5000RE (All…
CVE-2026-30783 — Critical (CVSS 9.8): A vulnerability in rustdesk-client RustDesk Client rustdesk-client on Windows, MacOS, Linux, iOS, Android, WebClient…
CVE-2026-23478 — Critical (CVSS 9.8): Cal.com is open-source scheduling software. From 3.1.6 to before 6.0.7, there is a vulnerability in a custom NextAuth…

Browse all CWE-602 vulnerabilities →