# CVE-2023-22952: Multiple SugarCRM Products Remote Code Execution

> Attackers can inject custom PHP code via crafted requests in SugarCRM EmailTemplates due to missing input validation, leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 2 Feb 2023 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jan 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-g9w6-c3gx-pmr3

## What is CVE-2023-22952?

CVE-2023-22952 is a high-severity code injection vulnerability in Sugarcrm Sugarcrm, published on 11 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In SugarCRM before 12.0. Hotfix 91155, a crafted request can inject custom PHP code through the EmailTemplates because of missing input validation.

Weakness: CWE-20 (Improper Input Validation), CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Sugarcrm Sugarcrm.

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

No fix has been published for CVE-2023-22952 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 23 Feb 2023.

## Is CVE-2023-22952 being exploited?

Yes. Attackers have exploited CVE-2023-22952 in the wild since at least 2 Feb 2023.

Public exploit code:

- SugarCRM unauthenticated Remote Code Execution (RCE) (metasploit)
- SugarCRM Unauthenticated - Remote Code Execution (nuclei): http/cves/2023/CVE-2023-22952.yaml

## Other vulnerabilities in Sugarcrm Sugarcrm

- [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)
- [CVE-2018-6308](https://insights.sbomify.com/CVE-2018-6308/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22952 is a high-severity code injection vulnerability in Sugarcrm Sugarcrm, published on 11 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-22952 in the wild since at least 2 Feb 2023.

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

## Sources

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

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