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

> Attackers can execute arbitrary code remotely on Sitecore Experience Manager, Platform, and Commerce products.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2023
- **Updated:** 17 Dec 2024
- **Also known as:** GHSA-q6mf-24rq-66wc

## What is CVE-2023-35813?

CVE-2023-35813 is a critical code injection vulnerability in n/a, published on 17 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple Sitecore products allow remote code execution. This affects Experience Manager, Experience Platform, and Experience Commerce through 10.3.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 4 products.


Products: Sitecore Experience Commerce, Sitecore Experience Manager, Sitecore Experience Platform, Sitecore Managed Cloud.

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

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

## Is CVE-2023-35813 being exploited?

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

Public exploit code:

- Exploit for CVE-2023-35813 POC (github_poc): https://github.com/aalexpereira/CVE-2023-35813
- An exploit for the Sitecore Remote Code Execution Vulnerability (github_poc): https://github.com/BagheeraAltered/CVE-2023-35813-PoC
- CVE-2023-35813 is a proof-of-concept used to determine if an instance of Sitecore is vulnerable by analyzing a server Response Header for modification. (github_poc): https://github.com/her3ticAVI/CVE-2023-35813
- Exploit CVE-2023-35813 PoC Script (github_poc): https://github.com/Rezy-Dev/CVE-2023-35813
- https://github.com/nmlz/CVE-2023-35813_PoC (github_poc): https://github.com/nmlz/CVE-2023-35813_PoC
- Sitecore - Remote Code Execution (nuclei): http/cves/2023/CVE-2023-35813.yaml

## Other vulnerabilities in n/a

- [CVE-2025-53690](https://insights.sbomify.com/CVE-2025-53690/): Sitecore Multiple Products Deserialization of Untrusted Data (critical 9.0, exploited in the wild)
- [CVE-2025-53693](https://insights.sbomify.com/CVE-2025-53693/): HTML Cache Poisoning through Unsafe Reflections (critical 9.8)
- [CVE-2025-53691](https://insights.sbomify.com/CVE-2025-53691/): Sitecore Experience Remote Code Execution through Insecure Deserialization (high 8.8)
- [CVE-2025-34510](https://insights.sbomify.com/CVE-2025-34510/): Sitecore XM, XC, and XP Post-Auth RCE via Zip Slip (high 8.8)
- [CVE-2025-34511](https://insights.sbomify.com/CVE-2025-34511/): Sitecore PowerShell Extension RCE via Unrestricted Upload (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-35813 is a critical code injection vulnerability in n/a, published on 17 Jun 2023. 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-2023-35813 exists.

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

## Sources

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

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