CVE-2021-42092
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in Zammad before 4.1.1. Stored XSS may occur via an Article during addition of an attachment to a Ticket.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStored XSS vulnerability in Zammad before version 4.1.1 allows malicious script injection through the Article component when adding attachments to tickets. The application fails to properly sanitize attachment-related input, allowing persisted scripts to execute when other users view affected articles.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Zammad versionLocate the installed Zammad version through the admin interface (System > Info) or by querying the package manager/version file, then compare it against the vulnerable range (any version before 4.1.1)Affected if The installed version is below 4.1.1
-
Verify Article module is in useConfirm that the Zammad installation actively uses the ticket system and that users can create or modify tickets with the Article component (the module handling ticket communications and attachments)Affected if The ticket system with Article functionality is enabled and accessible to users
-
Inspect existing ticket articles for suspicious contentReview ticket articles in the database or through the admin interface, specifically examining attachment metadata and content fields for injected script tags or encoded malicious payloadsAffected if Any ticket articles contain unsanitized script tags, event handlers, or other XSS vectors in attachment-related fields
-
Check recent audit logs for XSS indicatorsReview Zammad audit logs and user activity logs for patterns indicating exploitation attempts, such as unusual HTML/script injection in ticket fields or attachment descriptionsAffected if Logs show patterns of script injection attempts in ticket or attachment fields
You are affected if your Zammad installation version is below 4.1.1 and the ticket system with Article attachments is in use, as the vulnerability allows stored XSS through unsanitized attachment input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.1.1
Upgrade Zammad to version 4.1.1 or later, which includes proper input sanitization for attachment handling in the Article module.
4.1.1
- Upgrade Zammad to version 4.1.1 or later to resolve the stored XSS vulnerability in attachment handling
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-42092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-42092 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data