Back to Database
Status published
Medium
CVE-2020-26035
An issue was discovered in Zammad before 3.4.1. There is...
Vulnerability Description
An issue was discovered in Zammad before 3.4.1. There is Stored XSS via a Tags element in a TIcket.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2020-26035
Credits & Attribution
No credits recorded in the NVD database.
More from zammad
View All →CVE-2022-48023
Insufficient privilege verification in Zammad v5.3.0 allows an authenticated attacker...
Medium
4.3
CVE-2022-48022
An issue in the component /api/v1/mentions of Zammad v5.3.0 allows...
Unknown
0
CVE-2022-48021
A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary...
Unknown
0
CVE-2022-40817
Zammad 5.2.1 has a fine-grained permission model that allows to...
Unknown
0
CVE-2022-40816
Zammad 5.2.1 is vulnerable to Incorrect Access Control. Zammad's asset...
Unknown
0
Affected Vendor
zammad
View all reports →Affected Software
zammad
Vulnerable Versions:
1.0.0
Timeline
Official Publish:
December 28th, 2020
Last Modified:
August 4th, 2024
Added to House:
July 21st, 2026
CVSS Vectors
V3:
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.