CVE-2026-34721

Zammad has Cross-site request forgery (CSRF) in OAuth callback endpoints

Published Apr 8, 2026 CVSS 4.0 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1 and 6.5.4, the OAuth callback endpoints for Microsoft, Google, and Facebook external credentials do not validate a CSRF state parameter. This vulnerability is fixed in 7.0.1 and 6.5.4.

Analysis

AI-generated

Technical impact

The identified flaw resides in Zammad's OAuth callback endpoints for Microsoft, Google, and Facebook. Because the applications fail to verify the CSRF state parameter, an attacker can forge requests that the server will accept as legitimate. This permits the unauthorized execution of actions tied to an authenticated user, potentially resulting in compromised user sessions or unauthorized access to internal resources.

Affected Systems

The affected product is Zammad Zammad. Versions prior to 7.0.1 in the 7.x branch and prior to 6.5.4 in the 6.x branch are vulnerable. These releases were distributed as open‑source web applications that provide customer support functionality.

Risk and Exploitability

With a CVSS score of 5.9 the severity is moderate. EPSS information is not available and the vulnerability is not listed in the CISA KEV catalog. The attack requires an active HTTP session of a logged‑in user and a malicious site to issue a crafted request to the callback endpoint; this inference is drawn from the absence of state validation. An attacker who can coerce users into visiting a malicious host can exploit the vulnerability to perform unauthorized actions through the authenticated session.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Zammad 7.0.1 or 6.5.4 to address the CSRF validation issue.
  • If an upgrade cannot be performed immediately, restrict external access to the OAuth callback endpoints using firewall or web‑application configuration so that only trusted domains can initiate requests.
  • Verify that your current installation validates the CSRF state parameter before accepting OAuth callbacks.
  • Monitor the installation for signs of unauthorized OAuth usage and keep the vendor’s advisories under review.

Generated by OpenCVE AI on April 8, 2026 at 19:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:*
cpe:2.3:a:zammad:zammad:7.0.0:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Zammad
Zammad zammad
Vendors & Products Zammad
Zammad zammad
Type Values Removed Values Added
Description Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1 and 6.5.4, the OAuth callback endpoints for Microsoft, Google, and Facebook external credentials do not validate a CSRF state parameter. This vulnerability is fixed in 7.0.1 and 6.5.4.
Title Zammad has Cross-site request forgery (CSRF) in OAuth callback endpoints
Weaknesses CWE-352
References
Metrics cvssV4_0

{'score': 5.9, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Apr 9, 2026, 2:22 PM
Reserved
Mar 30, 2026, 6:41 PM
Status
Analyzed
Published
Apr 8, 2026, 7:25 PM
Modified
Jul 24, 2026, 10:10 PM