# CVE-2025-25034: SugarCRM PHP Deserialization RCE

> Unauthenticated attackers can achieve arbitrary code execution in SugarCRM by submitting malicious serialized data due to improper input validation.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2025
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-wcx8-f39f-5c87

## What is CVE-2025-25034?

CVE-2025-25034 is a critical unsafe deserialization vulnerability in SugarCRM, published on 20 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-25034?


## How do I fix CVE-2025-25034?

No fix has been published for CVE-2025-25034 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-25034 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25034 exists.

Public exploit code:

- SugarCRM REST Unserialize PHP Code Execution (metasploit)
- SugarCRM - Unauthenticated Remote Code Execution via PHP Object Injection (nuclei): http/cves/2025/CVE-2025-25034.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-25034 and fix it if it is affected.

What it is: CVE-2025-25034 is a critical unsafe deserialization vulnerability in SugarCRM, published on 20 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25034 exists.

Affected product: SugarCRM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-25034/ (Markdown: https://insights.sbomify.com/CVE-2025-25034/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-25034
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-25034
- OSV: https://osv.dev/vulnerability/CVE-2025-25034

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-25034/
Summaries are generated and may contain mistakes; the official description above is the record.