CVE-2020-26035: XSS
First published: Mon Dec 28 2020(Updated: )
An issue was discovered in Zammad before 3.4.1. There is Stored XSS via a Tags element in a TIcket.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Zammad Zammad | >=1.0.0<3.4.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-26035?
The severity of CVE-2020-26035 is medium, with a severity value of 5.4.
How does CVE-2020-26035 affect Zammad?
CVE-2020-26035 affects Zammad versions before 3.4.1.
What type of vulnerability is CVE-2020-26035?
CVE-2020-26035 is a stored XSS vulnerability.
How can the vulnerability in CVE-2020-26035 be exploited?
The vulnerability in CVE-2020-26035 can be exploited by injecting malicious code into the Tags element in a Ticket in Zammad.
How can I fix CVE-2020-26035?
To fix CVE-2020-26035, upgrade Zammad to version 3.4.1 or later.
- collector/nvd-index
- agent/severity
- agent/weakness
- agent/references
- agent/author
- agent/type
- agent/event
- agent/description
- agent/softwarecombine
- agent/last-modified-date
- agent/tags
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- vendor/zammad
- canonical/zammad zammad
- version/zammad zammad/1.0.0