Undisclosed RCE in Zammad v6.3 and higher

Local privilege escalation in Zammad v1.5.0 to v7.2.2 installed via DEB or RPM package

A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted message sent to the server

Zammad 5.2.0 is vulnerable to privilege escalation

An issue was discovered in Zammad before 4.1.1

An issue was discovered in Zammad before 4.1.1

An issue was discovered in Zammad before 3.4.1

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 Access-Control headers

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

Zammad: Account takeover via unverified email matching during SSO auto-link

An issue was discovered in Zammad before 6.3.0

An access control issue in Zammad v5.0.3 allows attackers to write entries to the CTI caller log without authentication

An issue was discovered in Zammad before 4.1.1

Zammad: Arbitrary File Deletion via Unvalidated Session Identifier in Long Polling Controller

In Zammad 6.4.x before 6.4.2, there is client-side enforcement of server-side security

An issue was discovered in Zammad before 4.1.1

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

Zammad: Denial of Service via OTRS Import Controller

Zammad: Incorrect Authorization and Improper Privilege Management

Zammad: AI Agent template sanitizer bypass leads to remote code execution

An issue was discovered in Zammad before 6.3.0

Zammad: Cross-Site Scripting in Ticket Notifications

In Zammad 6.4.x before 6.4.2, there is information exposure

With certain LDAP configurations, Zammad 5.0.1 was found to be vulnerable to unauthorized access with existing user accounts

Zammad has incorrect access control in getting_started_controller

An issue was discovered in Zammad before 6.2.0

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 known account to cause Denial Of…

Zammad 5.2.0 suffers from Incorrect Access Control

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 legitimate user, leading to a…

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 (DoS) during password verification

An issue was discovered in Zammad before 4.1.1

Incorrect Access Control in Zammad 1.0.x up to 4.0.0 allows attackers to obtain sensitive information via email connection configuration probing

An issue was discovered in Zammad before 3.5.1

An SSRF issue was discovered in Zammad before 3.4.1

An issue was discovered in Zammad 3.0 through 3.2

An issue was discovered in Zammad 3.0 through 3.2

Zammad has a server-side template injection leading to RCE via AI Agent

An issue was discovered in Zammad before 4.1.1

Zammad: S/MIME signature verification allows forged sender impersonation

Zammad: IDOR in External Data Source rendering exposes ticket, user, group, and organization data

Zammad: PGP signature spoofing via unvalidated verification return

Zammad: Missing authorization on ticket attachment download

Zammad: Incorrect implementation of permission checks in the knowledge base module

Zammad 7.0.1 - Improper authorization in ticket article attachment cloning

Zammad: Missing rate limiting allows password brute-forcing during two-factor login

Zammad: Sensitive Information Exposure in Integration Administration API

In Zammad before 6.3.1, a Ruby gem bundled by Zammad is installed with world-writable file permissions

Zammad has Cross-site request forgery (CSRF) in OAuth callback endpoints

An issue was discovered in Zammad before 6.3.0

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