Security readout for executives and security teams
Plain-English summary
Older Zammad helpdesk versions could run JavaScript from an email subject when a user opened a ticket. For a business, the main concern is staff exposure while handling tickets. The source says this was fixed in Zammad 2.3.1, 2.2.2, and 2.1.3.
Executive priority
Treat this as a time-bounded remediation item for any legacy Zammad deployment. It is not KEV-listed in the bundle, but the affected versions are old and fixed releases are named.
Technical view
CVE-2018-1000154 is an HTML/script neutralization flaw in Zammad 2.3.0 and earlier. Email subjects were not HTML-quoted in certain cases, allowing JavaScript to execute in a user browser when a ticket was opened. The record describes CWE-80 behavior, but provides no CVSS score.
Likely exposure
Exposure is limited to organizations running Zammad 2.3.0 or earlier. Risk is most relevant where Zammad ingests email subjects into tickets viewed by agents or other authenticated users.
Exploitation context
The source states exploitation appears possible when a victim opens a ticket. The bundle does not cite public exploitation, KEV listing, exploit maturity, or real-world abuse.
Researcher notes
The provided record names Zammad versions 2.3.0 and earlier and describes script execution through insufficient quoting of email subjects. Affected CPEs, CVSS metrics, and detailed patch mechanics are not included in the bundle.
Mitigation direction
- Upgrade affected Zammad deployments to 2.3.1, 2.2.2, 2.1.3, or later supported versions.
- Review Zammad advisory ZAA-2018-01 and release notes for branch-specific guidance.
- Prioritize patching systems that process inbound email into support tickets.
- Check vendor guidance before applying any non-upgrade workaround.
Validation and detection
- Inventory all Zammad instances and record exact running versions.
- Confirm no deployment remains on Zammad 2.3.0 or earlier.
- Review ticketing workflows that display inbound email subjects to users.
- Check change records for upgrade completion to a fixed release.
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.
CVE-2018-1000154 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/issues/1869CVE reference · x_refsource_CONFIRM
- https://zammad.com/news/release-2-4CVE reference · x_refsource_CONFIRM
- https://zammad.com/news/security-advisory-zaa-2018-01CVE reference · x_refsource_CONFIRM
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.