Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Zimbra | Collaboration Suite |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.209% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Synacor
Synacor zimbra Collaboration Suite |
|
| CPEs | cpe:2.3:a:synacor:zimbra_collaboration_suite:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Synacor
Synacor zimbra Collaboration Suite |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Cross‑Site Request Forgery Allowing Unauthorized Account State Changes in Zimbra Collaboration |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Zimbra
Zimbra collaboration Suite |
|
| Vendors & Products |
Zimbra
Zimbra collaboration Suite |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Cross‑Site Request Forgery Allowing Unauthorized Account State Changes in Zimbra Collaboration | |
| Weaknesses | CWE-352 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An issue was discovered in Zimbra Collaboration (ZCS) 10.0 and 10.1. A Cross-Site Request Forgery (CSRF) vulnerability exists in Zimbra Web Client due to the issuance of authentication tokens without CSRF protection during certain account state transitions. Specifically, tokens generated after operations such as enabling two-factor authentication or changing a password may lack CSRF enforcement. While such a token is active, authenticated SOAP requests that trigger token generation or state changes can be performed without CSRF validation. An attacker could exploit this by inducing a victim to submit crafted requests, potentially allowing sensitive account actions such as disabling two-factor authentication. The issue is mitigated by ensuring CSRF protection is consistently enforced for all issued authentication tokens. | |
| References |
|