Loading vulnerability…
CVE-2025-25034 is a PHP object injection vulnerability in SugarCRM versions prior to 6.5.24, 6.7.13, 7.5.2.5, 7.6.2.2, and 7.7.1.0. The issue is in SugarRestSerialize.php, where the application improperly validates PHP serialized input and passes the user-controlled rest_data parameter to PHP's unserialize() function without adequate sanitization. An unauthenticated attacker can supply crafted serialized payloads containing malicious object declarations, which can trigger unsafe object instantiation and magic-method execution during deserialization, leading to arbitrary code execution in the application context. The content indicates this issue persisted despite an earlier fix referenced in advisory sugarcrm-sa-2016-001, which was incomplete and did not address all exploitation vectors. Exploitation in the wild was observed by the Shadowserver Foundation on 2024-09-13 UTC.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (Ruby file) that exploits a PHP Object Injection vulnerability (CVE-2025-25034) in SugarCRM CE versions 6.5.23 and earlier. The exploit targets the vulnerable REST endpoint at /service/v4/rest.php, abusing the unserialize() call in the SugarRestSerialize.php script. By sending a crafted serialized object, the exploit leverages the __destruct() method of the SugarCacheFile class to write a PHP webshell into the /custom directory of the target application. The webshell allows arbitrary PHP code execution via a custom HTTP header. The module is operational and provides remote code execution capabilities to the attacker. The repository is structured as a typical Metasploit exploit module, with all logic contained in a single Ruby file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.