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

> Attackers can execute arbitrary code by uploading a crafted PNG file to the BlogEngine.NET application.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-mfh9-9gwj-9822

## What is CVE-2022-41418?

CVE-2022-41418 is a high-severity vulnerability in n/a, published on 19 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue in the component BlogEngine/BlogEngine.NET/AppCode/Api/UploadController.cs of BlogEngine.NET v3.3.8.0 allows attackers to execute arbitrary code via uploading a crafted PNG file.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Blogengine Blogengine.net.

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

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

## Is CVE-2022-41418 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-33404](https://insights.sbomify.com/CVE-2023-33404/): File upload in n/a (critical 9.8)
- [CVE-2022-41417](https://insights.sbomify.com/CVE-2022-41417/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-14485](https://insights.sbomify.com/CVE-2018-14485/): XML external entity in n/a (critical 9.8)
- [CVE-2019-6714](https://insights.sbomify.com/CVE-2019-6714/): Path traversal in n/a (critical 9.8)
- [CVE-2022-25591](https://insights.sbomify.com/CVE-2022-25591/): Path traversal in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41418 is a high-severity vulnerability in n/a, published on 19 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41418 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-2022-41418/ (Markdown: https://insights.sbomify.com/CVE-2022-41418/index.md)
```

## Sources

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

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