CVE-2026-33372
Received Received - Intake
CSRF Vulnerability in Zimbra Webmail Allows Unauthorized Actions

Publication date: 2026-03-20

Last updated on: 2026-04-01

Assigner: MITRE

Description
An issue was discovered in Zimbra Collaboration (ZCS) 10.0 and 10.1. A cross-site request forgery (CSRF) vulnerability exists in Zimbra Webmail due to improper validation of CSRF tokens. The application accepts CSRF tokens supplied within the request body instead of requiring them through the expected request header. An attacker can exploit this issue by tricking an authenticated user into submitting a crafted request. This may allow unauthorized actions to be performed on behalf of the victim.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-20
Last Modified
2026-04-01
Generated
2026-05-07
AI Q&A
2026-03-20
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
synacor zimbra_collaboration_suite From 10.0.0 (inc) to 10.1.16 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a cross-site request forgery (CSRF) issue found in Zimbra Collaboration (ZCS) versions 10.0 and 10.1. It occurs because the Zimbra Webmail application improperly validates CSRF tokens by accepting them from the request body instead of requiring them in the expected request header.

An attacker can exploit this by tricking an authenticated user into submitting a specially crafted request, which may allow the attacker to perform unauthorized actions on behalf of that user.


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized actions being performed on your behalf without your consent if an attacker successfully tricks you into submitting a malicious request while authenticated.

  • Potential unauthorized changes to your account or data.
  • Compromise of account integrity and security.
  • Possible exposure to further attacks leveraging the unauthorized actions.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart