# CVE-2023-35810: Code injection in n/a

> Admin users can execute arbitrary PHP code via second-order object injection in the DocuSign module due to missing input validation.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2023
- **Updated:** 17 Dec 2024
- **Also known as:** GHSA-mqpw-mc8r-75fm

## What is CVE-2023-35810?

CVE-2023-35810 is a high-severity code injection vulnerability in Sugarcrm Sugarcrm, published on 17 Jun 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in SugarCRM Enterprise before 11.0.6 and 12.x before 12.0.3. A Second-Order PHP Object Injection vulnerability has been identified in the DocuSign module. By using crafted requests, custom PHP code can be injected and executed through the DocuSign module because of missing input validation. Admin user privileges are required to exploit this vulnerability. Editions other than Enterprise are also affected.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2023-35810?

It affects 1 product.


Products: Sugarcrm Sugarcrm.

## How do I fix CVE-2023-35810?

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

## Is CVE-2023-35810 being exploited?

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

## Other vulnerabilities in Sugarcrm Sugarcrm

- [CVE-2023-22952](https://insights.sbomify.com/CVE-2023-22952/): Multiple SugarCRM Products Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2004-1225](https://insights.sbomify.com/CVE-2004-1225/): SQL injection in n/a (critical 10.0)
- [CVE-2020-7472](https://insights.sbomify.com/CVE-2020-7472/): Path traversal in n/a (critical 9.8)
- [CVE-2012-0694](https://insights.sbomify.com/CVE-2012-0694/): Deserialization in n/a (critical 9.8)
- [CVE-2014-3244](https://insights.sbomify.com/CVE-2014-3244/): XML external entity in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35810 and fix it if it is affected.

What it is: CVE-2023-35810 is a high-severity code injection vulnerability in Sugarcrm Sugarcrm, published on 17 Jun 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35810 exists.

Affected product: Sugarcrm 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-2023-35810/ (Markdown: https://insights.sbomify.com/CVE-2023-35810/index.md)
```

## Sources

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

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