CVE-2025-25034
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-06-20

Last updated on: 2025-11-20

Assigner: VulnCheck

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-20
Last Modified
2025-11-20
Generated
2026-05-07
AI Q&A
2025-06-21
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a PHP object injection in SugarCRM versions prior to 6.5.24, 6.7.13, 7.5.2.5, 7.6.2.2, and 7.7.1.0. It occurs because the application improperly validates PHP serialized input in the SugarRestSerialize.php script. Specifically, the rest_data parameter is not sanitized before being passed to the unserialize() function, allowing an unauthenticated attacker to submit crafted serialized data containing malicious object declarations. This can lead to arbitrary code execution within the application context.


How can this vulnerability impact me? :

This vulnerability can allow an unauthenticated attacker to execute arbitrary code within the context of the SugarCRM application. This could lead to full compromise of the application, unauthorized access to sensitive data, disruption of services, and potentially further attacks on the underlying system or network.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart