# CVE-2023-38915: File upload in n/a

> A remote attacker can execute arbitrary code via the upload type function in Wolf-leo EasyAdmin8.

- **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:** 15 Aug 2023
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-pw8m-qp4c-vv96

## What is CVE-2023-38915?

CVE-2023-38915 is a critical vulnerability in n/a, published on 15 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

File Upload vulnerability in Wolf-leo EasyAdmin8 v.1.0 allows a remote attacker to execute arbtirary code via the upload type function.

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

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

It affects 1 product.


Products: Wolf18 Easyadmin8.

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

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

## Is CVE-2023-38915 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38915 is a critical vulnerability in n/a, published on 15 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-38915 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-2023-38915/ (Markdown: https://insights.sbomify.com/CVE-2023-38915/index.md)
```

## Sources

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

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