VYPR

Zammad

by Zammad

Source repositories

CVEs (125)

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

Page 4 of 7