Security readout for executives and security teams
Plain-English summary
Older Zammad helpdesk versions can run malicious JavaScript in a user's browser when the user opens a ticket. This creates risk to helpdesk users and possibly sensitive ticket data. The sources name fixed versions, but do not show active exploitation.
Executive priority
Treat this as a targeted cleanup item, not an emergency based on current evidence. Prioritize any exposed or business-critical Zammad systems because helpdesk tickets often contain sensitive operational and customer information.
Technical view
CVE-2019-1010018 is a CWE-80 cross-site scripting issue in the Zammad web app affecting Zammad 2.3.0 and earlier. The documented attack vector requires a victim to open a ticket. Fixed versions are listed as 2.3.1, 2.2.2, and 2.1.3.
Likely exposure
Exposure is limited to organizations still running affected Zammad versions, especially user-facing support portals where untrusted ticket content may be opened by agents.
Exploitation context
The bundle states the victim must open a ticket and JavaScript may execute in the browser. KEV is false, and no cited source in the bundle establishes active exploitation.
Researcher notes
The CVE record gives affected versions, impact, component, attack vector, CWE, and fixed versions. It does not provide CVSS details, proof of exploitation, or detailed remediation beyond fixed releases.
Mitigation direction
- Inventory Zammad deployments and confirm exact versions.
- Upgrade affected branches to 2.3.1, 2.2.2, 2.1.3, or later supported releases.
- Prioritize public support portals and high-volume ticketing environments.
- Restrict access to legacy instances until upgrade is complete.
- Check Zammad vendor guidance if the upgrade path is constrained.
Validation and detection
- Verify deployed Zammad versions are newer than the affected releases.
- Confirm remediation against the relevant Zammad compare references.
- Review ticket handling paths for untrusted content rendering.
- Check logs for suspicious ticket content or unusual agent-session behavior.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-80: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-1010018 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/zammad/zammad/compare/ea50d0c...238784dCVE reference · x_refsource_MISC
- https://github.com/zammad/zammad/compare/5c983f6...1a9af7dCVE reference · x_refsource_MISC
- https://github.com/zammad/zammad/issues/1869CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.