# CVE-2022-38916: Pagekit vulnerable to Unrestricted Upload of File with Dangerous Type

> An attacker can upload malicious files via the storage feature in Pagekit, potentially leading to remote code execution.

- **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:** 20 Sep 2022
- **Updated:** 27 May 2025
- **Also known as:** GHSA-4v5m-vwvp-p7w8

## What is CVE-2022-38916?

CVE-2022-38916 is a critical vulnerability in n/a, published on 20 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A file upload vulnerability exists in the storage feature of pagekit 1.0.18, which allows an attacker to upload malicious files

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

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

2 open source packages ship an affected version, including pagekit/pagekit. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pagekit/pagekit` | Packagist | All versions to 1.0.18 | None |
| `pagekit/pagekit` | Packagist | All versions to 1.0.18 | None |

Products: Pagekit Pagekit.

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

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

## Is CVE-2022-38916 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38916 exists.

## Other vulnerabilities in n/a

- [CVE-2025-67164](https://insights.sbomify.com/CVE-2025-67164/): Pagekit CMS is vulnerable to OS Command Injection via Storage component (critical 9.9)
- [CVE-2025-67165](https://insights.sbomify.com/CVE-2025-67165/): Pagekit CMS has an Insecure Direct Object Reference (IDOR) in its User Role component (critical 9.8)
- [CVE-2021-44135](https://insights.sbomify.com/CVE-2021-44135/): SQL injection in pagekit/pagekit (critical 9.8)
- [CVE-2019-19013](https://insights.sbomify.com/CVE-2019-19013/): Pagekit File Upload vulnerability (high 8.8)
- [CVE-2023-41005](https://insights.sbomify.com/CVE-2023-41005/): Command injection in pagekit (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38916 is a critical vulnerability in n/a, published on 20 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-38916 exists.

Affected packages and fixed versions:
- pagekit/pagekit (Packagist): affected all versions up to 1.0.18; no fix listed
- pagekit/pagekit (Packagist): affected all versions up to 1.0.18; 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-38916/ (Markdown: https://insights.sbomify.com/CVE-2022-38916/index.md)
```

## Sources

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

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