CVE-2025-25064 in the critical feed json
SQL injection vulnerability in the ZimbraSync Service SOAP endpoint in Zimbra Collaboration 10.0.x before 10.0.12 and 10.1.x before 10.1.4…
published last yr. modified 4mo ago also EUVD-2025-4006
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 36.7%
- EPSS 36.7% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
SQL injection vulnerability in the ZimbraSync Service SOAP endpoint in Zimbra Collaboration 10.0.x before 10.0.12 and 10.1.x before 10.1.4 due to insufficient sanitization of a user-supplied parameter. Authenticated attackers can exploit this vulnerability by manipulating a specific parameter in the request, allowing them to inject arbitrary SQL queries that could retrieve email metadata.
Patch / fix
- synacor zimbra_collaboration_suite 10.0.12, 10.1.4
Is CVE-2025-25064 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
36.73% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
wiki.zimbra.com
/wiki/Zimbra_Security_Advisories
vendor-advisory
-
wiki.zimbra.com
/wiki/Zimbra_Releases/10.1.4#Security_Fixes
release-notes
-
wiki.zimbra.com
/wiki/Zimbra_Releases/10.0.12#Security_Fixes
release-notes
Sources
- CVE List CVE-2025-25064
- NVD CVE-2025-25064
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.