How severe is CVE-2025-32360?

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

Is CVE-2025-32360 being actively exploited?

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

What products are affected by CVE-2025-32360?

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

How do I fix CVE-2025-32360?

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

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

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

When was CVE-2025-32360 published?

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

CVE-2025-32360

CVE-2025-32360 is a medium-severity vulnerability in Zammad with a CVSS 3.x base score of 4.2. 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-402.

Key facts

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

Description

In Zammad 6.4.x before 6.4.2, there is information exposure. Only agents should be able to see and work on shared article drafts. However, a logged in customer was able to see details about shared drafts for their customer tickets in the browser console, which may contain confidential information, and also to manipulate them via API.

Frequently asked questions

What is CVE-2025-32360?: In Zammad 6.4.x before 6.4.2, there is information exposure. Only agents should be able to see and work on shared article drafts. However, a logged in customer was able to see details about shared drafts for their customer tickets in the browser console, which may contain confidential information, and also to manipulate them via API.
How severe is CVE-2025-32360?: CVE-2025-32360 has a CVSS 3.x base score of 4.2, rated medium severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2025-32360 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-32360?: CVE-2025-32360 affects Zammad. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-32360?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-32360 have an EU (EUVD) identifier?: Yes. CVE-2025-32360 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-14713.
When was CVE-2025-32360 published?: CVE-2025-32360 was published on 2025-04-05 and last updated on 2026-06-17.

References

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

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-402 vulnerabilities

CVE-2025-0502 — Critical (CVSS 9.1): Transmission of Private Resources into a New Sphere ('Resource Leak') vulnerability in CrafterCMS Engine on Linux,…
CVE-2025-48383 — High (CVSS 8.2): Django-Select2 is a Django integration for Select2. Prior to version 8.4.1, instances of HeavySelect2Mixin subclasses…
CVE-2024-29900 — High (CVSS 7.5): Electron Packager bundles Electron-based application source code with a renamed Electron executable and supporting…
CVE-2022-3596 — High (CVSS 7.5): An information leak was found in OpenStack's undercloud. This flaw allows unauthenticated, remote attackers to inspect…
CVE-2025-67745 — High (CVSS 7.1): MyHoard is a daemon for creating, managing and restoring MySQL backups. Starting in version 1.0.1 and prior to version…
CVE-2024-47146 — Medium (CVSS 6.5): Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x could allow an attacker to obtain the devices serial…

Browse all CWE-402 vulnerabilities →