Vulnerability database
Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.
123 results · page 3 of 3
Dec 28, 2020An issue was discovered in Zammad before 3.4.1.CVE-2020-26031 · Other software · Zammad · reported by MITREMedium 4.3
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).
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Dec 28, 2020An issue was discovered in Zammad before 3.4.1.CVE-2020-26030 · Other software · Zammad · reported by MITRECritical 9.8
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 configured. An attacker can create a valid and authenticated session that can be used to perform any actions in the name of other users.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Dec 28, 2020An issue was discovered in Zammad before 3.4.1.CVE-2020-26029 · Other software · Zammad · reported by MITREMedium 6.5
An issue was discovered in Zammad before 3.4.1. There are wrong authorization checks for impersonation requests via X-On-Behalf-Of. The authorization checks are performed for the actual user and not the one given in the X-On-Behalf-Of header.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Dec 28, 2020An issue was discovered in Zammad before 3.4.1.CVE-2020-26028 · Other software · Zammad · reported by MITREMedium 4.9
An issue was discovered in Zammad before 3.4.1. Admin Users without a ticket.* permission can access Tickets.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 16, 2020Zammad before 3.3.1, when Domain Based Assignment is enabled, relies on a claimed e-mail address for authorization decisions.CVE-2020-14214 · Other software · Zammad · reported by MITREMedium 6.5
Zammad before 3.3.1, when Domain Based Assignment is enabled, relies on a claimed e-mail address for authorization decisions. An attacker can register a new account that will have access to all tickets of an arbitrary Organization.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jun 16, 2020In 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-14213 · Other software · Zammad · reported by MITREMedium 5.4
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).
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10105 · Other software · Zammad · reported by MITREMedium 5.3
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 404.html (/zammad/public/404.html)
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10104 · Other software · Zammad · reported by MITREMedium 4.3
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 used by an attacker to gain unauthorized access. Hashed passwords are returned to the user when visiting a certain URL.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An XSS issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10103 · Other software · Zammad · reported by MITREMedium 5.4
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 file with an active Zammad session.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10102 · Other software · Zammad · reported by MITREMedium 5.3
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 supplied was recognized as associated with a valid user. This behavior could be used as part of a two-stage automated attack. During the first stage, an attacker would iterate through a list of account names to determine which correspond to valid accounts. During the second stage, the attacker would use a list of common passwords to attempt to brute force credentials for accounts that were recognized by the system in the first stage.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10101 · Other software · Zammad · reported by MITREHigh 7.5
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 message format is not properly checked and parsing errors not handled. This leads to a crash of the service process.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10100 · Other software · Zammad · reported by MITREMedium 6.5
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, the application does not properly implement access controls related to this functionality. As such, users of one company are able to access ticket data from other companies. Due to the multi-tenant nature of this application, users who can access ticket details from one organization to the next allows for users to exfiltrate potentially sensitive data of other companies.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An XSS issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10099 · Other software · Zammad · reported by MITREMedium 5.4
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 Toolbar.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An XSS issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10098 · Other software · Zammad · reported by MITREMedium 5.4
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.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10097 · Other software · Zammad · reported by MITREMedium 5.3
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.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 4, 2020An issue was discovered in Zammad 3.0 through 3.2.CVE-2020-10096 · Other software · Zammad · reported by MITREHigh 7.5
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 remotely compromises or obtains physical access to a user's workstation can browse the browser cache contents and obtain sensitive information. The attacker does not need to be authenticated with the application to view this information, as it would be available via the browser cache.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Jul 16, 2019Zammad GmbH Zammad 2.3.0 and earlier is affected by: Cross Site Scripting (XSS) - CWE-80.CVE-2019-1010018 · Other software · Zammad GmbH · reported by josh@bress.netMedium 6.1
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.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Apr 5, 2018Zammad 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 CVE-2018-1000154 · Other software · Zammad · reported by MITREMedium 6.1
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 code on users browser. This attack appear to be exploitable via the victim openning a ticket. This vulnerability appears to have been fixed in 2.3.1, 2.2.2 and 2.1.3.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Mar 13, 2017A 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.CVE-2017-6081 · Other software · Zammad · reported by MITREHigh 8.8
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 cross-domain requests directly to the REST API for users with a valid session cookie.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordsecurityfocus.comzammad.com
Mar 13, 2017An 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-ContrCVE-2017-6080 · Other software · Zammad · reported by MITRECritical 9.8
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. To exploit the vulnerability, an attacker can send cross-domain requests directly to the REST API for users with a valid session cookie and receive the result.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordsecurityfocus.comzammad.com
Mar 13, 2017An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1.CVE-2017-5621 · Other software · Zammad · reported by MITREMedium 6.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. 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.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordsecurityfocus.comzammad.com
Mar 13, 2017An 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.CVE-2017-5620 · Other software · Zammad · reported by MITREMedium 6.1
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.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordsecurityfocus.comzammad.com
Mar 13, 2017An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1.CVE-2017-5619 · Other software · Zammad · reported by MITRECritical 9.8
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 (e.g., from the DB) instead of the valid password string.
- Product
- Zammad
- What to do
- Apply the vendor’s update. The NVD record links to the advisory.
Full record and what to do →NVD recordsecurityfocus.comzammad.com
Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.