dbcve.org
ZammadApplication

CVE-2023-50456

MEDIUM · 5.3 CVSS v3.1 Published 2023-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in Zammad before 6.2.0. An attacker can trigger phishing links in generated notification emails via a crafted first or last name.

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 · moderate confidence

In Zammad before 6.2.0, the application fails to properly sanitize or validate first and last name fields when generating notification emails. An attacker with the ability to set their name (e.g., as a customer or user in the system) can inject malicious links into these name fields, which then appear in outgoing notification emails sent to other users, enabling phishing attacks.

MitigationUpgrade Zammad to version 6.2.0 or later, which includes proper input validation/sanitization for name fields used in email generation.

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
ZammadApplication
Affected:= 6.1.0= 6.2.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Zammad version
    Access the Zammad admin panel and navigate to the About or System Information section, or run the command-line tool to retrieve the Zammad version (e.g., 'zammad --version' or check the package manager).
    Affected if The installed version is earlier than 6.2.0 (e.g., 6.1.0, 6.0.x, or earlier).
  2. Verify email notifications are enabled
    In the Zammad admin panel, navigate to the Notification > Email settings or similar configuration area to confirm outgoing email notifications are configured and active.
    Affected if Email notifications are enabled and Zammad is earlier than version 6.2.0.
  3. Confirm user profile name fields are accessible
    Check if users or customers can edit their own profile first and last name fields through the user settings or customer portal interface.
    Affected if Users can modify their own name fields and Zammad is earlier than version 6.2.0.
  4. Inspect outgoing notification email content
    Trigger a notification email (e.g., by creating a ticket or updating a user profile) and examine the raw email headers and body to see if name fields are rendered without sanitization.
    Affected if The notification email contains unsanitized user-provided first or last name data, especially if the name appears as a clickable link or contains HTML markup.

A user is affected if their Zammad installation is version 6.1.0 or earlier, has email notifications enabled, and allows users to modify their name fields which then appear unsanitized in outgoing emails.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Zammad to version 6.2.0 or later, which includes proper input validation/sanitization for name fields used in email generation.

Recommended fix Moderate confidence

6.3.0 or later (latest stable release)

  1. 1. Backup your Zammad database and configuration files before upgrading
  2. 2. Review the Zammad upgrade documentation for your current version
  3. 3. Upgrade Zammad to version 6.3.0 or later (the first version after the vulnerable 6.2.0 release)
  4. 4. After upgrade, verify that user first/last name fields properly sanitize input to prevent open redirect injection
  5. 5. Test that notification emails render user names correctly without malicious redirect links
Caveat Review Zammad 6.3.0 release notes for any migration requirements or configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zammad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50456 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50456 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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