# CVE-2019-19013: Pagekit File Upload vulnerability

> An attacker can upload arbitrary files to Pagekit by bypassing CSRF protection, potentially compromising the web application.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-692x-89xv-64jx

## What is CVE-2019-19013?

CVE-2019-19013 is a high-severity vulnerability in n/a, published on 22 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A CSRF vulnerability in Pagekit 1.0.17 allows an attacker to upload an arbitrary file by removing the CSRF token from a request.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-19013?

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.17 | None |
| `pagekit/pagekit` | Packagist | All versions to 1.0.17 | None |

Products: Pagekit Pagekit.

## How do I fix CVE-2019-19013?

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

## Is CVE-2019-19013 being exploited?

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

## 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-2022-38916](https://insights.sbomify.com/CVE-2022-38916/): Pagekit vulnerable to Unrestricted Upload of File with Dangerous Type (critical 9.8)
- [CVE-2021-44135](https://insights.sbomify.com/CVE-2021-44135/): SQL injection in pagekit/pagekit (critical 9.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-2019-19013 and fix it if it is affected.

What it is: CVE-2019-19013 is a high-severity vulnerability in n/a, published on 22 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-19013 in the wild and no public exploit code.

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

## Sources

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

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