# CVE-2018-14519: Kirby CMS 2.5.12 Cross-site Request Forgery

> A remote attacker can force a user to delete pages via a crafted CSRF request in the Kirby CMS delete page functionality.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **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:** 24 Aug 2022
- **Updated:** 4 Jul 2026
- **Also known as:** GHSA-c7x2-7h8r-jq4m

## What is CVE-2018-14519?

CVE-2018-14519 is a medium-severity vulnerability in n/a, published on 24 Aug 2022. 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

An issue was discovered in Kirby 2.5.12. The delete page functionality suffers from a CSRF flaw. A remote attacker can craft a malicious CSRF page and force the user to delete a page.

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

## Which versions are affected by CVE-2018-14519?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `getkirby/cms` | Packagist | All versions to 2.5.12 | None |
| `getkirby/cms` | Packagist | All versions to 2.5.12 | None |

Products: Getkirby Kirby.

## How do I fix CVE-2018-14519?

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

## Is CVE-2018-14519 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-26483](https://insights.sbomify.com/CVE-2024-26483/): Kirby vulnerable to unrestricted file upload of user avatar images (high 8.8)
- [CVE-2024-41964](https://insights.sbomify.com/CVE-2024-41964/): Insufficient permission checks in the language settings in Kirby CMS (high 8.1)
- [CVE-2026-34587](https://insights.sbomify.com/CVE-2026-34587/): Kirby has Server-Side Template Injection (SSTI) via double template resolution in option rendering (high 7.6)
- [CVE-2021-29460](https://insights.sbomify.com/CVE-2021-29460/): Cross-site scripting (XSS) from unsanitized uploaded SVG files (high 7.6)
- [CVE-2023-38489](https://insights.sbomify.com/CVE-2023-38489/): Kirby vulnerable to Insufficient Session Expiration after a password change (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14519 and fix it if it is affected.

What it is: CVE-2018-14519 is a medium-severity vulnerability in n/a, published on 24 Aug 2022. 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-2018-14519 in the wild and no public exploit code.

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

## Sources

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

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