dbcve.org
ZammadApplication

CVE-2025-32360

HIGH · 8.1 CVSS v3.1 Published 2025-04-05
Fix available
A fix is available. Upgrade to 6.4.2 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Zammad 6.4.x before 6.4.2 contains an authorization bypass where authenticated customers can view and manipulate shared article drafts intended only for agent access. The vulnerability exposes confidential information through the browser console and allows API-based modification of these drafts, representing a privilege escalation and information disclosure flaw.

MitigationUpgrade Zammad to version 6.4.2 or later to address the authorization bypass. Review access logs for unauthorized draft access and reset any potentially exposed credentials or data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZammadApplication
Affected:>= 6.4.0, < 6.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Zammad installation version
    Check the installed Zammad version by running `zammad run rails r "puts Rails.root"` to find the root, then look at version.rb or run `zammad version` if available. Alternatively, check the package manager: `dpkg -l | grep zammad` or `rpm -qa | grep zammad`
    Affected if Installed version is >= 6.4.0 and < 6.4.2
  2. Confirm customer account type exists
    Log into Zammad as a customer (end-user) account and verify you can access the system. The vulnerability affects authenticated customer accounts
    Affected if Customer accounts exist in the system and can log in
  3. Check for shared article draft functionality
    As a customer user, attempt to access shared draft articles via the web UI or API endpoint /api/v1/articles or /api/v1/tickets. Look for drafts that should only be visible to agent accounts
    Affected if Customer accounts can view or list article drafts that belong to agent-only tickets or shared draft content
  4. Review access logs for draft endpoint access
    Examine Zammad access logs (typically in /var/log/zammad or via the admin interface) for API calls to draft-related endpoints from customer user agents. Search for unusual GET/PUT/POST requests to article endpoints by non-agent users
    Affected if Logs show customer accounts accessing article/draft endpoints that should be restricted to agents
  5. Verify API token usage by customer accounts
    Check API token usage logs or audit logs for customer-associated tokens making requests to ticket/article endpoints that modify draft content
    Affected if Customer API tokens are being used to create, read, or modify article drafts

A Zammad installation is affected if it runs version 6.4.0 or 6.4.1 AND customer accounts can access or modify article drafts intended for agent-only access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.4.2 or later
Fixed in 6.4.2
Interim mitigation

Upgrade Zammad to version 6.4.2 or later to address the authorization bypass. Review access logs for unauthorized draft access and reset any potentially exposed credentials or data.

Recommended fix High confidence

6.4.2

  1. Verify current Zammad version is >= 6.4.0 and < 6.4.2 by checking the admin interface or running: zammad --version
  2. Create a complete backup of the Zammad database and application files before upgrading
  3. For production environments, test the upgrade in a staging environment first
  4. Upgrade Zammad to version 6.4.2 or later by following the official upgrade documentation for your installation method (package-based or source)
  5. After upgrade, verify the version is correctly installed: zammad --version
  6. Log in as an agent and verify that shared article drafts are no longer accessible to customer users via the API endpoint used in the exploit

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zammad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32360 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data