VYPR

Vendor CVEs

Zammad

All CVEs

125 total · sorted by risk
  • CVE-2021-35298MedJun 28, 2021
    risk 0.40cvss 6.1epss 0.01

    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 contain a 'note' field to store additional information.

  • CVE-2019-1010018MedJul 16, 2019
    risk 0.40cvss 6.1epss 0.01

    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. The component is: web app. The attack vector is: the victim must open a ticket. The fixed version is: 2.3.1, 2.2.2 and 2.1.3.

  • CVE-2018-1000154MedApr 5, 2018
    risk 0.40cvss 6.1epss 0.02

    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 the subject of emails which are not html quoted in certain cases. This can result in the embedding and execution of java script…

  • CVE-2017-5621MedMar 13, 2017
    risk 0.40cvss 6.1epss 0.01

    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 message or the content of a ticket article, when using either the REST API or the WebSocket API.

  • CVE-2017-5620MedMar 13, 2017
    risk 0.40cvss 6.1epss 0.01

    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 getting downloaded. This creates an attack vector of executing code in the domain of the application.

  • CVE-2026-84465HigSep 25, 2026
    risk 0.39cvss —epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when Zammad checks the digital signature on an incoming S/MIME-signed email, it does not verify that the signing certificate is genuinely trusted, it only checks whether a certificate with a…

  • CVE-2026-84464HigSep 25, 2026
    risk 0.39cvss —epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, zammad's External Data Source feature, used to look up records from an external system, did not properly verify whether a user was allowed to see a specific ticket, user, group, or organization…

  • CVE-2026-56727HigSep 25, 2026
    risk 0.39cvss —epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, summary In Zammad's inbound PGP email processing, the return value of the gpg verification call was silently discarded. Regardless of whether gpg reported a valid, invalid, or missing signature,…

  • CVE-2026-56724HigSep 25, 2026
    risk 0.39cvss —epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, summary An issue with permission checks in the knowledge base management area has been identified. Under certain conditions, data validation for linked items was not fully enforced. This could…

  • CVE-2026-56723HigSep 25, 2026
    risk 0.39cvss —epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, a customer who can view a ticket cannot see internal ticket articles through the article listing API. However, the same customer can directly request an attachment belonging to an internal…

  • CVE-2026-84461MedSep 25, 2026
    risk 0.38cvss —epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, the two-factor login step let an attacker try unlimited password guesses for any account without triggering Zammad's normal lockout or rate limiting. The response also revealed whether a guess…

  • CVE-2026-63207MedSep 25, 2026
    risk 0.38cvss —epss 0.00

    Zammad is a web based open source helpdesk/customer support system. In 7.0.3 and 7.1.1, an authenticated administrator can obtain stored integration credentials in cleartext through the integration administration API. Certain responses do not consistently mask sensitive fields,…

  • CVE-2023-50454MedDec 10, 2023
    risk 0.38cvss 5.9epss 0.00

    An issue was discovered in Zammad before 6.2.0. In several subsystems, SSL/TLS was used to establish connections to external services without proper validation of hostname and certificate authority. This is exploitable by man-in-the-middle attackers.

  • CVE-2026-34248MedApr 8, 2026
    risk 0.37cvss 5.7epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1, customers in shared organizations (means they can see each other's tickets) could see fields which are not intended for customers - including fields not intended for them at all (e.g. priority,…

  • CVE-2026-34721MedApr 8, 2026
    risk 0.35cvss 6.5epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1 and 6.5.4, the OAuth callback endpoints for Microsoft, Google, and Facebook external credentials do not validate a CSRF state parameter. This vulnerability is fixed in 7.0.1 and 6.5.4.

  • CVE-2021-44886MedFeb 4, 2022
    risk 0.35cvss 5.3epss 0.01

    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 the original agent, they could receive ticket notifications for tickets that they have no access to.

  • CVE-2021-42137MedOct 11, 2021
    risk 0.35cvss 5.3epss 0.01

    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 tickets that shows title, state, etc.

  • CVE-2021-42085MedOct 7, 2021
    risk 0.35cvss 5.4epss 0.01

    An issue was discovered in Zammad before 4.1.1. There is stored XSS via a custom Avatar.

  • CVE-2021-42092MedOct 7, 2021
    risk 0.35cvss 5.4epss 0.01

    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.

  • CVE-2021-35302MedJun 28, 2021
    risk 0.35cvss 5.3epss 0.01

    Incorrect Access Control for linked Tickets in Zammad 1.0.x up to 4.0.0 allows remote attackers to obtain sensitive information.

  • CVE-2021-35301MedJun 28, 2021
    risk 0.35cvss 5.3epss 0.01

    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.

  • CVE-2020-26035MedDec 28, 2020
    risk 0.35cvss 5.4epss 0.01

    An issue was discovered in Zammad before 3.4.1. There is Stored XSS via a Tags element in a TIcket.

  • CVE-2020-26033MedDec 28, 2020
    risk 0.35cvss 5.4epss 0.00

    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.

  • CVE-2020-14213MedJun 16, 2020
    risk 0.35cvss 5.4epss 0.01

    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).

  • CVE-2020-10105MedMar 5, 2020
    risk 0.35cvss 5.3epss 0.01

    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 request. Disclosure of source code allows for an attacker to formulate more precise attacks. Source code was disclosed for the file…

  • CVE-2020-10103MedMar 5, 2020
    risk 0.35cvss 5.4epss 0.01

    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 functionality in Zammad. The malicious JavaScript will execute within the browser of any user who opens a specially crafted link to the uploaded…

  • CVE-2020-10102MedMar 5, 2020
    risk 0.35cvss 5.3epss 0.01

    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 guess valid user emails. In the current implementation, the application responds differently depending on whether the input…

  • CVE-2020-10099MedMar 5, 2020
    risk 0.35cvss 5.4epss 0.01

    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 Zammad. The malicious JavaScript will execute within the browser of any user who opens the ticket or has the ticket within the…

  • CVE-2020-10098MedMar 5, 2020
    risk 0.35cvss 5.4epss 0.01

    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 malicious JavaScript will execute within the browser of any user who opens the Ticket with the Article created from that Email.

  • CVE-2020-10097MedMar 5, 2020
    risk 0.35cvss 5.3epss 0.01

    An issue was discovered in Zammad 3.0 through 3.2. It may respond with verbose error messages that disclose internal application or infrastructure information. This information could aid attackers in successfully exploiting other vulnerabilities.

  • CVE-2026-84463MedSep 25, 2026
    risk 0.34cvss —epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, a user with Knowledge Base editing rights for a category can embed a video widget in a published answer with a specially crafted value. When the answer is rendered, that value is inserted into…

  • CVE-2023-50456MedDec 10, 2023
    risk 0.34cvss 5.3epss 0.00

    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 name.

  • CVE-2023-50453MedDec 10, 2023
    risk 0.34cvss 5.3epss 0.01

    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 configuration data of user object attributes, such as selectable values, which should not be visible to the public.

  • CVE-2026-34718MedApr 8, 2026
    risk 0.33cvss 6.1epss 0.00

    Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1 and 6.5.4, the HTML sanitizer for ticket articles was missing proper sanitization of data: ... URI schemes, resulting in storing such malicious content in the database of the Zammad instance. The…

  • CVE-2021-42087MedOct 7, 2021
    risk 0.32cvss 4.9epss 0.01

    An issue was discovered in Zammad before 4.1.1. An admin can discover the application secret via the API.

  • CVE-2020-29159MedDec 28, 2020
    risk 0.32cvss 4.9epss 0.01

    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 admin. This behvaior was unintended.

  • CVE-2020-26028MedDec 28, 2020
    risk 0.32cvss 4.9epss 0.01

    An issue was discovered in Zammad before 3.4.1. Admin Users without a ticket.* permission can access Tickets.

  • CVE-2025-32359MedApr 5, 2025
    risk 0.31cvss 4.8epss 0.00

    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…

  • CVE-2026-130384MedNov 17, 2026
    risk 0.28cvss 4.3epss 0.00

    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…

  • CVE-2025-32357MedApr 5, 2025
    risk 0.28cvss 4.3epss 0.00

    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 that they have no permission for.

  • CVE-2024-55578MedDec 9, 2024
    risk 0.28cvss 4.3epss 0.00

    Zammad before 6.4.1 places sensitive data (such as auth_microsoft_office365_credentials and application_secret) in log files.

  • CVE-2023-50457MedDec 10, 2023
    risk 0.28cvss 4.3epss 0.00

    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 user could see entries for which they lack permissions.

  • CVE-2022-48023MedFeb 3, 2023
    risk 0.28cvss 4.3epss 0.00

    Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker to perform changes on the tags of their customer tickets using the Zammad API. This is now corrected in v5.3.1 so that only agents with write permissions may change ticket tags.

  • CVE-2022-48022MedFeb 3, 2023
    risk 0.28cvss 4.3epss 0.01

    An issue in the component /api/v1/mentions of Zammad v5.3.0 allows authenticated attackers with agent permissions to view information about tickets they are not authorized to see.

  • CVE-2022-40817MedSep 27, 2022
    risk 0.28cvss 4.3epss 0.01

    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 perform some operations on such tickets, like adding and removing links, tags. and related answers. This issue has been fixed in…

  • CVE-2022-27331MedApr 27, 2022
    risk 0.28cvss 4.3epss 0.01

    An access control issue in Zammad v5.0.3 broadcasts administrative configuration changes to all users who have an active application instance, including settings that should only be visible to authenticated users.

  • CVE-2021-35300MedJun 28, 2021
    risk 0.28cvss 4.3epss 0.01

    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 attackers' page.

  • CVE-2020-29158MedDec 28, 2020
    risk 0.28cvss 4.3epss 0.01

    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 Articles via the Ticket detail view.

  • CVE-2020-26034MedDec 28, 2020
    risk 0.28cvss 4.3epss 0.01

    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 anonymous user to guess valid user email addresses. The application responds differently depending on whether the input supplied was…

  • CVE-2020-26031MedDec 28, 2020
    risk 0.28cvss 4.3epss 0.01

    An issue was discovered in Zammad before 3.4.1. The global-search feature leaks Knowledge Base drafts to Knowledge Base readers (who are authenticated but have insufficient permissions).