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

> Attackers can execute arbitrary code by uploading a crafted image file to the S-Cart admin panel editor module.

- **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:** 1 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3w3q-6vq7-6wq8

## What is CVE-2021-38847?

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

### Official description

S-Cart v6.4.1 and below was discovered to contain an arbitrary file upload vulnerability in the Editor module on the Admin panel. This vulnerability allows attackers to execute arbitrary code via a crafted IMG file.

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

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

It affects 1 product.


Products: S-Cart S-Cart.

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

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

## Is CVE-2021-38847 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28456](https://insights.sbomify.com/CVE-2020-28456/): Cross-site Scripting (XSS) (high 7.3)
- [CVE-2020-28457](https://insights.sbomify.com/CVE-2020-28457/): Cross-site Scripting (XSS) (high 7.2)
- [CVE-2022-21149](https://insights.sbomify.com/CVE-2022-21149/): Cross-site Scripting (XSS) (medium 5.4)
- [CVE-2021-44111](https://insights.sbomify.com/CVE-2021-44111/): Path Traversal in S-Cart (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-38847 is a high-severity vulnerability in n/a, published on 1 Nov 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-38847 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-38847/ (Markdown: https://insights.sbomify.com/CVE-2021-38847/index.md)
```

## Sources

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

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