Quick answers
- Is CVE-2026-63213 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63213 being exploited in the wild.
- How severe is CVE-2026-63213?
- High severity, with a CVSS score of 7.2, published 5 November 2026.
- Which products and versions are affected?
- SuiteCRM prior to 7.15.2 and 8.10.2.
- Is there a fix for CVE-2026-63213?
- Yes: fixed in 7.15.2, 8.10.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63213 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-63213?
- Check whether you run SuiteCRM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 7.15.2, 8.10.2
Technical details
The Upgrade Wizard's commit flow trusts an unsanitized hidden zip_to_dir parameter without proper validation; the clean_path() function fails to reject directory traversal sequences (e.g., ../). An authenticated administrator can craft a malicious package archive to extract files outside the destination directory, enabling file overwrite, arbitrary PHP execution in the web root, or denial of service.
Affected products
- SuiteCRM SuiteCRM prior to 7.15.2 and 8.10.2
Timeline
- 2026-11-05: published
- 2026-07-29: patched: Fix commit date from GitHub repository