CVE-2025-25034: SugarCRM · Deserialization of Untrusted Data
Affects SugarCRMSource CVE Database V5
Public exploit available (Metasploit) · CVSS 9.3 Critical · fixed in 7.7.1.0 : patch SugarCRM as a priority.
Data as of 29 Oct 2026, 20:45 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 9.3 |
|---|
- CISA SSVC
- Exploitation
- Proof of concept is public or traded
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2025-06-23.
- Patch
- Available – fixed in 7.7.1.0, 7.6.2.2, 7.5.2.5 +2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 20 Jun 2025
Detectable: evidence found.
nuclei template: SugarCRM - Unauthenticated Remote Code Execution via PHP Object Injection
Weaponized: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by VulnCheck
, 140 days before disclosure
CVE published
on cve.org
, t = 0
CISA SSVC assessment
proof of concept public
, 3 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SugarCRMSugarCRM | Affected
| Fixed in
|
| SugarCRMSugarCRM | Affected
| Fixed in
|
| SugarCRMSugarCRM | Affected
| Fixed in
|
| SugarCRMSugarCRM | Affected
| Fixed in
|
| SugarCRMSugarCRM | Affected
| Fixed in
|
Description
A PHP object injection vulnerability exists in SugarCRM versions prior to 6.5.24, 6.7.13, 7.5.2.5, 7.6.2.2, and 7.7.1.0 due to improper validation of PHP serialized input in the SugarRestSerialize.php script. The vulnerable code fails to sanitize the rest_data parameter before passing it to the unserialize() function. This allows an unauthenticated attacker to submit crafted serialized data containing malicious object declarations, resulting in arbitrary code execution within the application context. Although SugarCRM released a prior fix in advisory sugarcrm-sa-2016-001, the patch was incomplete and failed to address some vectors. Exploitation evidence was observed by the Shadowserver Foundation on 2024-09-13 UTC.
References
- web.archive.org/web/20160725194502/http://www.sugarcrm.com/security/sugarcrm-sa-2016-008 (opens in a new tab)
- web.archive.org/web/20160508053502/http://www.sugarcrm.com/security/sugarcrm-sa-2016-001 (opens in a new tab)
- karmainsecurity.com/KIS-2016-07 (opens in a new tab)
- exploit-db.com/exploits/40344 (opens in a new tab)
- raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/unix/webapp/sugarcrm_rest_unserialize_exec.rb (opens in a new tab)
- sugarcrm.com/crm/ (opens in a new tab)
- vulncheck.com/advisories/sugarcrm-php-deserialization-rce (opens in a new tab)