CVE-2026-130384 in Zammad
Summary
by MITRE • 11/17/2026
Zammad before 7.2.3 contains a missing authorization vulnerability that allows authenticated customers to delete agents' shared ticket drafts by supplying a shared_draft_id. Attackers can create tickets via POST /api/v1/tickets or reply to accessible tickets referencing a draft id, destroying draft text prepared by agents.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/17/2026
The identified security flaw in Zammad versions prior to 7.2.3 represents a critical failure in access control mechanisms, specifically categorized under CWE-862 Missing Authorization. This vulnerability stems from an insufficient validation of user permissions when processing requests related to shared ticket drafts. In the context of enterprise customer relationship management systems like Zammad, shared drafts are intended as collaborative tools for agents to prepare responses or create tickets efficiently. However, the application logic fails to verify whether the authenticated entity initiating a deletion request possesses the requisite administrative privileges or ownership rights over the specific draft resource being targeted.
The technical mechanism of this exploitation involves an attacker who has already obtained valid authentication credentials as a customer user. By constructing HTTP requests that target the internal API endpoints responsible for managing shared drafts, specifically by supplying a known or guessed shared_draft_id, the malicious actor can bypass intended restrictions. The system processes these deletion commands without adequately checking if the requesting user is authorized to modify or remove resources created and owned by agents. This lack of server-side authorization checks allows any authenticated customer with knowledge of the draft identifier to execute destructive actions against agent workflows.
The operational impact of this vulnerability extends beyond simple data loss, affecting business continuity and employee productivity. Agents often spend significant time composing detailed responses or preparing complex ticket structures using shared drafts. When these resources are deleted by unauthorized customers, it results in the immediate destruction of valuable work product that cannot be easily recovered if backups are not frequently maintained. Furthermore, this disruption can lead to delays in customer service operations as agents must reconstruct their prepared content from memory or notes, thereby increasing response times and potentially degrading the quality of support provided to end-users.
This vulnerability aligns with MITRE ATT&CK technique T1078 Valid Accounts, where adversaries leverage legitimate credentials to perform actions within a system that they should not be permitted to execute. It also reflects aspects of T1485 Data Destruction, as the primary outcome is the intentional deletion of data critical to organizational operations. The ability for lower-privileged users to impact higher-privileged workflows highlights a fundamental gap in role-based access control implementation within the application's API layer.
To mitigate this risk, organizations running Zammad versions earlier than 7.2.3 must prioritize immediate patching by upgrading to version 7.2.3 or later where these authorization checks have been corrected. In environments where immediate patching is not feasible due to operational constraints, temporary mitigations should include restricting API access through network-level controls such as firewalls or reverse proxies that limit exposure of the affected endpoints to trusted IP ranges only. Additionally, implementing strict input validation and ensuring that all API requests undergo rigorous server-side authorization verification against user roles can help prevent similar exploitation vectors in other parts of the application stack. Regular security audits focusing on access control logic are recommended to identify and remediate any remaining privilege escalation or unauthorized action vulnerabilities.