{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33372 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-33372 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33372 is a medium-severity vulnerability in Synacor Zimbra Collaboration Suite, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-33372 and fix it if it is affected.\n\nWhat it is: CVE-2026-33372 is a medium-severity vulnerability in Synacor Zimbra Collaboration Suite, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-33372 in the wild and no public exploit code.\n\nAffected product: Synacor Zimbra Collaboration Suite. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33372/ (Markdown: https://insights.sbomify.com/CVE-2026-33372/index.md)","id":"CVE-2026-33372","markdown":"https://insights.sbomify.com/CVE-2026-33372/index.md","name":"CVE-2026-33372","record":{"aliases":["GHSA-fmww-x8fc-gqfj"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Zimbra Collaboration","requires_auth":"none","summary":"Attackers can perform unauthorized actions on behalf of authenticated users via CSRF due to improper token validation in Zimbra Webmail.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"zimbra_collaboration_suite","vendor":"synacor"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2026-33372","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"synacor:zimbra_collaboration_suite","products":["synacor:zimbra_collaboration_suite"],"type":"csrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2026-33373"},"packages":[],"prev":{"headline":"XML external entity in n/a","id":"CVE-2026-33371"},"products":["n/a"],"published":"2026-03-20","related":[{"cvss_score":10,"headline":"Synacor Zimbra Collaboration Suite (ZCS) Command Execution","id":"CVE-2024-45519","kev_date_added":"2024-10-03","published":"2024-10-02"},{"cvss_score":9.8,"headline":"Synacor Zimbra Collaboration Suite (ZCS) Arbitrary File Upload","id":"CVE-2022-41352","kev_date_added":"2022-10-20","published":"2022-09-26"},{"cvss_score":9.8,"headline":"Synacor Zimbra Collaboration Suite (ZCS) Authentication Bypass","id":"CVE-2022-37042","kev_date_added":"2022-08-11","published":"2022-08-11"},{"cvss_score":9.8,"headline":"Synacor Zimbra Collaboration Suite (ZCS) Command Injection","id":"CVE-2022-27924","kev_date_added":"2022-08-04","published":"2022-04-20"},{"cvss_score":9.8,"headline":"Synacor Zimbra Collaboration Suite (ZCS) Server-Side Request Forgery","id":"CVE-2020-7796","kev_date_added":"2026-02-17","published":"2020-02-18"},{"cvss_score":9.8,"headline":"Synacor Zimbra Collaboration Suite (ZCS) Improper Restriction of XML External Entity Reference","id":"CVE-2019-9670","kev_date_added":"2022-01-10","published":"2019-05-29"},{"cvss_score":9,"headline":"Synacor Zimbra Collaboration Suite (ZCS) Cross-Site Scripting (XSS)","id":"CVE-2023-34192","kev_date_added":"2025-02-25","published":"2023-07-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-23","vendors":["n/a"]},"summary":"Attackers can perform unauthorized actions on behalf of authenticated users via CSRF due to improper token validation in Zimbra Webmail.","url":"https://insights.sbomify.com/CVE-2026-33372/"}