Zammad
80 vulnerabilities.
All published vulnerabilities with a CVE number in Zammad products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2025-32360 | Zammad: 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 … | 2025-04-05 | 4.2 |
| CVE-2025-32359 | Zammad: In Zammad 6.4.x before 6.4.2, there is client-side enforcement of server-side security. When changing their two factor authentication … | 2025-04-05 | 4.8 |
| CVE-2025-32358 | Zammad: In Zammad 6.4.x before 6.4.2, SSRF can occur. Authenticated admin users can enable webhooks in Zammad, which are triggered as POST requests when … | 2025-04-05 | 4.0 |
| CVE-2025-32357 | Zammad: In Zammad 6.4.x before 6.4.2, an authenticated agent with knowledge base permissions was able to use the Zammad API to fetch knowledge base content … | 2025-04-05 | 4.3 |
| CVE-2024-55578 | Zammad: Zammad before 6.4.1 places sensitive data (such as auth_microsoft_office365_credentials and application_secret) in log files. | 2024-12-09 | 4.3 |
| CVE-2024-36078 | Zammad: In Zammad before 6.3.1, a Ruby gem bundled by Zammad is installed with world-writable file permissions. This allowed a local attacker on the server … | 2024-05-19 | 6.7 |
| CVE-2024-33668 | Zammad: An issue was discovered in Zammad before 6.3.0. The Zammad Upload Cache uses insecure, partially guessable FormIDs to identify content. An attacker … | 2024-04-25 | 9.1 |
| CVE-2024-33667 | Zammad: An issue was discovered in Zammad before 6.3.0. An authenticated agent could perform a remote Denial of Service attack by calling an endpoint that … | 2024-04-25 | 6.5 |
| CVE-2024-33666 | Zammad: An issue was discovered in Zammad before 6.3.0. Users with customer access to a ticket could have accessed time accounting details of this ticket … | 2024-04-25 | 8.6 |
| CVE-2023-50457 | Zammad: An issue was discovered in Zammad before 6.2.0. When listing tickets linked to a knowledge base answer, or knowledge base answers of a ticket, a … | 2023-12-10 | 4.3 |
| CVE-2023-50456 | Zammad: An issue was discovered in Zammad before 6.2.0. An attacker can trigger phishing links in generated notification emails via a crafted first or last … | 2023-12-10 | 5.3 |
| CVE-2023-50455 | Zammad: An issue was discovered in Zammad before 6.2.0. Due to lack of rate limiting in the "email address verification" feature, an attacker could send … | 2023-12-10 | 7.5 |
| CVE-2023-50454 | Zammad: An issue was discovered in Zammad before 6.2.0. In several subsystems, SSL/TLS was used to establish connections to external services without … | 2023-12-10 | 5.9 |
| CVE-2023-50453 | Zammad: An issue was discovered in Zammad before 6.2.0. It uses the public endpoint /api/v1/signshow for its login screen. This endpoint returns internal … | 2023-12-10 | 5.3 |
| CVE-2023-31597 | Zammad: An issue in Zammad v5.4.0 allows attackers to bypass e-mail verification using an arbitrary address and manipulate the data of the generated user. … | 2023-05-18 | 6.5 |
| CVE-2023-29868 | Zammad: Zammad 5.3.x (Fixed in 5.4.0) is vulnerable to Incorrect Access Control. An authenticated attacker with agent and customer roles could perform … | 2023-05-02 | 6.5 |
| CVE-2023-29867 | Zammad: Zammad 5.3.x (Fixed 5.4.0) is vulnerable to Incorrect Access Control. An authenticated attacker could gain information about linked accounts of … | 2023-05-02 | 6.5 |
| CVE-2022-48023 | Zammad: Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker to perform changes on the tags of their customer tickets … | 2023-02-03 | 4.3 |
| CVE-2022-48022 | Zammad: An issue in the component /api/v1/mentions of Zammad v5.3.0 allows authenticated attackers with agent permissions to view information about tickets … | 2023-02-03 | 4.3 |
| CVE-2022-48021 | Zammad: A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted message sent to the server. | 2023-02-03 | 9.8 |
| CVE-2022-40817 | Zammad: Zammad 5.2.1 has a fine-grained permission model that allows to configure read-only access to tickets. However, agents were still wrongly able to … | 2022-09-27 | 4.3 |
| CVE-2022-40816 | Zammad: Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset handling mechanism has logic to ensure that customer users are not able to … | 2022-09-27 | 6.5 |
| CVE-2022-35490 | Zammad: Zammad 5.2.0 is vulnerable to privilege escalation. Zammad has a prevention against brute-force attacks trying to guess login credentials. After a … | 2022-08-08 | 9.8 |
| CVE-2022-35489 | Zammad: In Zammad 5.2.0, customers who have secondary organizations assigned were able to see all organizations of the system rather than only those to … | 2022-08-08 | 6.5 |
| CVE-2022-35488 | Zammad: In Zammad 5.2.0, an attacker could manipulate the rate limiting in the 'forgot password' feature of Zammad, and thereby send many requests for a … | 2022-08-08 | 7.5 |
| CVE-2022-35487 | Zammad: Zammad 5.2.0 suffers from Incorrect Access Control. Zammad did not correctly perform authorization on certain attachment endpoints. This could be … | 2022-08-08 | 7.5 |
| CVE-2022-29701 | Zammad: A lack of rate limiting in the 'forgot password' feature of Zammad v5.1.0 allows attackers to send an excessive amount of reset requests for a … | 2022-04-27 | 7.5 |
| CVE-2022-29700 | Zammad: A lack of password length restriction in Zammad v5.1.0 allows for the creation of extremely long passwords which can cause a Denial of Service … | 2022-04-27 | 7.5 |
| CVE-2022-27332 | Zammad: An access control issue in Zammad v5.0.3 allows attackers to write entries to the CTI caller log without authentication. This vulnerability can … | 2022-04-27 | 9.1 |
| CVE-2022-27331 | Zammad: An access control issue in Zammad v5.0.3 broadcasts administrative configuration changes to all users who have an active application instance, … | 2022-04-27 | 4.3 |
| CVE-2021-44886 | Zammad: In Zammad 5.0.2, agents can configure "out of office" periods and substitute persons. If the substitute persons didn't have the same permissions as … | 2022-02-04 | 5.3 |
| CVE-2021-43145 | Zammad: With certain LDAP configurations, Zammad 5.0.1 was found to be vulnerable to unauthorized access with existing user accounts. | 2022-02-04 | 8.1 |
| CVE-2021-42137 | Zammad: An issue was discovered in Zammad before 5.0.1. In some cases, there is improper enforcement of the privilege requirement for viewing a list of … | 2021-10-11 | 5.3 |
| CVE-2021-42094 | Zammad: An issue was discovered in Zammad before 4.1.1. Command Injection can occur via custom Packages. | 2021-10-07 | 9.8 |
| CVE-2021-42093 | Zammad: An issue was discovered in Zammad before 4.1.1. An admin can execute code on the server via a crafted request that manipulates triggers. | 2021-10-07 | 7.2 |
| CVE-2021-42092 | Zammad: An issue was discovered in Zammad before 4.1.1. Stored XSS may occur via an Article during addition of an attachment to a Ticket. | 2021-10-07 | 5.4 |
| CVE-2021-42091 | Zammad: An issue was discovered in Zammad before 4.1.1. SSRF can occur via GitHub or GitLab integration. | 2021-10-07 | 9.1 |
| CVE-2021-42090 | Zammad: An issue was discovered in Zammad before 4.1.1. The Form functionality allows remote code execution because deserialization is mishandled. | 2021-10-07 | 9.8 |
| CVE-2021-42089 | Zammad: An issue was discovered in Zammad before 4.1.1. The REST API discloses sensitive information. | 2021-10-07 | 7.5 |
| CVE-2021-42088 | Zammad: An issue was discovered in Zammad before 4.1.1. The Chat functionality allows XSS because clipboard data is mishandled. | 2021-10-07 | 6.1 |
| CVE-2021-42087 | Zammad: An issue was discovered in Zammad before 4.1.1. An admin can discover the application secret via the API. | 2021-10-07 | 4.9 |
| CVE-2021-42086 | Zammad: An issue was discovered in Zammad before 4.1.1. An Agent account can modify account data, and gain admin access, via a crafted request. | 2021-10-07 | 8.8 |
| CVE-2021-42085 | Zammad: An issue was discovered in Zammad before 4.1.1. There is stored XSS via a custom Avatar. | 2021-10-07 | 5.4 |
| CVE-2021-42084 | Zammad: An issue was discovered in Zammad before 4.1.1. An attacker with valid agent credentials may send a series of crafted requests that cause an … | 2021-10-07 | 6.5 |
| CVE-2021-35303 | Zammad: Cross Site Scripting (XSS) in Zammad 1.0.x up to 4.0.0 allows remote attackers to execute arbitrary web script or HTML via the User Avatar attribute. | 2021-06-28 | 6.1 |
| CVE-2021-35302 | Zammad: Incorrect Access Control for linked Tickets in Zammad 1.0.x up to 4.0.0 allows remote attackers to obtain sensitive information. | 2021-06-28 | 5.3 |
| CVE-2021-35301 | Zammad: Incorrect Access Control in Zammad 1.0.x up to 4.0.0 allows remote attackers to obtain sensitive information via the Ticket Article detail view. | 2021-06-28 | 5.3 |
| CVE-2021-35300 | Zammad: Text injection/Content Spoofing in 404 page in Zammad 1.0.x up to 4.0.0 could allow remote attackers to manipulate users into visiting the … | 2021-06-28 | 4.3 |
| CVE-2021-35299 | Zammad: Incorrect Access Control in Zammad 1.0.x up to 4.0.0 allows attackers to obtain sensitive information via email connection configuration probing. | 2021-06-28 | 7.5 |
| CVE-2021-35298 | Zammad: Cross Site Scripting (XSS) in Zammad 1.0.x up to 4.0.0 allows remote attackers to execute arbitrary web script or HTML via multiple models that … | 2021-06-28 | 6.1 |
| CVE-2020-29160 | Zammad: An issue was discovered in Zammad before 3.5.1. A REST API call allows an attacker to change Ticket Article data in a way that defeats auditing. | 2020-12-28 | 7.5 |
| CVE-2020-29159 | Zammad: An issue was discovered in Zammad before 3.5.1. The default signup Role (for newly created Users) can be a privileged Role, if configured by an … | 2020-12-28 | 4.9 |
| CVE-2020-29158 | Zammad: An issue was discovered in Zammad before 3.5.1. An Agent with Customer permissions in a Group can bypass intended access control on internal … | 2020-12-28 | 4.3 |
| CVE-2020-26035 | Zammad: An issue was discovered in Zammad before 3.4.1. There is Stored XSS via a Tags element in a TIcket. | 2020-12-28 | 5.4 |
| CVE-2020-26034 | Zammad: An account-enumeration issue was discovered in Zammad before 3.4.1. The Create User functionality is implemented in a way that would enable an … | 2020-12-28 | 4.3 |
| CVE-2020-26033 | Zammad: An issue was discovered in Zammad before 3.4.1. The Tag and Link REST API endpoints (for add and delete) lack a CSRF token check. | 2020-12-28 | 5.4 |
| CVE-2020-26032 | Zammad: An SSRF issue was discovered in Zammad before 3.4.1. The SMS configuration interface for Massenversand is implemented in a way that renders the … | 2020-12-28 | 7.5 |
| CVE-2020-26031 | Zammad: An issue was discovered in Zammad before 3.4.1. The global-search feature leaks Knowledge Base drafts to Knowledge Base readers (who are … | 2020-12-28 | 4.3 |
| CVE-2020-26030 | Zammad: An issue was discovered in Zammad before 3.4.1. There is an authentication bypass in the SSO endpoint via a crafted header, when SSO is not … | 2020-12-28 | 9.8 |
| CVE-2020-26029 | Zammad: An issue was discovered in Zammad before 3.4.1. There are wrong authorization checks for impersonation requests via X-On-Behalf-Of. The … | 2020-12-28 | 6.5 |
| CVE-2020-26028 | Zammad: An issue was discovered in Zammad before 3.4.1. Admin Users without a ticket.* permission can access Tickets. | 2020-12-28 | 4.9 |
| CVE-2020-14214 | Zammad: Zammad before 3.3.1, when Domain Based Assignment is enabled, relies on a claimed e-mail address for authorization decisions. An attacker can … | 2020-06-16 | 6.5 |
| CVE-2020-14213 | Zammad: In Zammad before 3.3.1, a Customer has ticket access that should only be available to an Agent (e.g., read internal data, split, or merge). | 2020-06-16 | 5.4 |
| CVE-2020-10105 | Zammad: An issue was discovered in Zammad 3.0 through 3.2. It returns source code of static resources when submitting an OPTIONS request, rather than a GET … | 2020-03-05 | 5.3 |
| CVE-2020-10104 | Zammad: An issue was discovered in Zammad 3.0 through 3.2. After authentication, it transmits sensitive information to the user that may be compromised and … | 2020-03-05 | 4.3 |
| CVE-2020-10103 | Zammad: An XSS issue was discovered in Zammad 3.0 through 3.2. Malicious code can be provided by a low-privileged user through the File Upload … | 2020-03-05 | 5.4 |
| CVE-2020-10102 | Zammad: An issue was discovered in Zammad 3.0 through 3.2. The Forgot Password functionality is implemented in a way that would enable an anonymous user to … | 2020-03-05 | 5.3 |
| CVE-2020-10101 | Zammad: An issue was discovered in Zammad 3.0 through 3.2. The WebSocket server crashes when messages in non-JSON format are sent by an attacker. The … | 2020-03-05 | 7.5 |
| CVE-2020-10100 | Zammad: An issue was discovered in Zammad 3.0 through 3.2. It allows for users to view ticket customer details associated with specific customers. However, … | 2020-03-05 | 6.5 |
| CVE-2020-10099 | Zammad: An XSS issue was discovered in Zammad 3.0 through 3.2. Malicious code can be provided by a low-privileged user through the Ticket functionality in … | 2020-03-05 | 5.4 |
| CVE-2020-10098 | Zammad: An XSS issue was discovered in Zammad 3.0 through 3.2. Malicious code can be provided by a low-privileged user through the Email functionality. The … | 2020-03-05 | 5.4 |
| CVE-2020-10097 | Zammad: An issue was discovered in Zammad 3.0 through 3.2. It may respond with verbose error messages that disclose internal application or infrastructure … | 2020-03-05 | 5.3 |
| CVE-2020-10096 | Zammad: An issue was discovered in Zammad 3.0 through 3.2. It does not prevent caching of confidential data within browser memory. An attacker who either … | 2020-03-05 | 7.5 |
| CVE-2019-1010018 | Zammad: Zammad GmbH Zammad 2.3.0 and earlier is affected by: Cross Site Scripting (XSS) - CWE-80. The impact is: Execute java script code on users browser. … | 2019-07-16 | 6.1 |
| CVE-2018-1000154 | Zammad: Zammad GmbH Zammad version 2.3.0 and earlier contains a Improper Neutralization of Script-Related HTML Tags in a Web Page (CWE-80) vulnerability in … | 2018-04-05 | 6.1 |
| CVE-2017-6081 | Zammad: A CSRF issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. To exploit the vulnerability, an attacker can send … | 2017-03-13 | 8.8 |
| CVE-2017-6080 | Zammad: 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 protection mechanism involving HTTP … | 2017-03-13 | 9.8 |
| CVE-2017-5621 | Zammad: 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. XSS can be triggered via malicious HTML in a chat … | 2017-03-13 | 6.1 |
| CVE-2017-5620 | Zammad: An XSS issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1. Attachments are opened in a new tab instead of … | 2017-03-13 | 6.1 |
| CVE-2017-5619 | Zammad: 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. Attackers can login with the hashed password itself … | 2017-03-13 | 9.8 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.