Zammad · weakness class
Cross-Site Request Forgery
5 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
Every one of the 5 is a mark on the map. Named now: 1 to 5, most at risk first.
- 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 expl…
- 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 t…
- 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.
- Zammad: Malicious input in Ticket Body Enables Session Termination
- Zammad has Cross-site request forgery (CSRF) in OAuth callback endpoints
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.