# CVE-2021-37221: File upload in n/a

> Remote attackers can upload arbitrary PHP files via account update or customer creation features, leading to 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:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mjc9-82w5-xm2q

## What is CVE-2021-37221?

CVE-2021-37221 is a high-severity vulnerability in n/a, published on 27 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A file upload vulnerability exists in Sourcecodester Customer Relationship Management System 1.0 via the account update option & customer create option, which could let a remote malicious user upload an arbitrary php file. .

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

## Which versions are affected by CVE-2021-37221?

It affects 1 product.


Products: Customer Relationship Management System Project Customer Relationship Management System.

## How do I fix CVE-2021-37221?

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

## Is CVE-2021-37221 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-43130](https://insights.sbomify.com/CVE-2021-43130/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-37221 and fix it if it is affected.

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

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

## Sources

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

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