# CVE-2022-38843: File upload in n/a

> Attackers can upload malicious files with any extension to execute arbitrary code on the EspoCRM server.

- **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:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** BIT-espocrm-2022-38843, GHSA-9hh7-36j4-5fcg

## What is CVE-2022-38843?

CVE-2022-38843 is a high-severity vulnerability in n/a, published on 16 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EspoCRM version 7.1.8 is vulnerable to Unrestricted File Upload allowing attackers to upload malicious file with any extension to the server. Attacker may execute these malicious files to run unintended code on the server to compromise the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2022-38843?

1 open source package ship an affected version, including espocrm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `espocrm` | Bitnami | From 7.1.8 to 7.1.8 | None |

Products: Espocrm Espocrm.

## How do I fix CVE-2022-38843?

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

## Is CVE-2022-38843 being exploited?

There is no known exploitation of CVE-2022-38843 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-7985](https://insights.sbomify.com/CVE-2014-7985/): Path traversal in n/a (critical 10.0)
- [CVE-2026-33656](https://insights.sbomify.com/CVE-2026-33656/): Path traversal in espocrm (critical 9.1)
- [CVE-2019-14351](https://insights.sbomify.com/CVE-2019-14351/): Information disclosure in n/a (high 8.8)
- [CVE-2020-37094](https://insights.sbomify.com/CVE-2020-37094/): EspoCRM 5.7.0 < 5.9.0 - Two-Factor Authentication Bypass via Auth Token Reuse Between Accounts with Identical Passwords (high 8.6)
- [CVE-2022-38844](https://insights.sbomify.com/CVE-2022-38844/): Code injection in n/a (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38843 and fix it if it is affected.

What it is: CVE-2022-38843 is a high-severity vulnerability in n/a, published on 16 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38843 in the wild and no public exploit code.

Affected packages and fixed versions:
- espocrm (Bitnami): affected from 7.1.8 up to 7.1.8; no fix listed

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

## Sources

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

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