# CVE-2018-11564: Pagekit Stored Cross-site Scripting

> Stored XSS in Pagekit allows attackers to execute arbitrary scripts via malicious SVG uploads, potentially leading to session hijacking or site defacement.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3rwj-v7jp-w542

## What is CVE-2018-11564?

CVE-2018-11564 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Jun 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Stored XSS in YOOtheme Pagekit 1.0.13 and earlier allows a user to upload malicious code via the picture upload feature. A user with elevated privileges could upload a photo to the system in an SVG format. This file will be uploaded to the system and it will not be stripped or filtered. The user can create a link on the website pointing to "/storage/poc.svg" that will point to http://localhost/pagekit/storage/poc.svg. When a user comes along to click that link, it will trigger a XSS attack.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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 | None |
| `pagekit/pagekit` | Packagist | All versions | None |

Products: Pagekit Pagekit.

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

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

## Is CVE-2018-11564 being exploited?

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

Public exploit code:

- exploit tool of CVE-2018-11564 (github_poc): https://github.com/GeunSam2/CVE-2018-11564
- Pagekit < 1.0.13 - Cross-Site Scripting Code Generator (exploitdb)

## 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-2019-19013](https://insights.sbomify.com/CVE-2019-19013/): Pagekit File Upload vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11564 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Jun 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-11564 in the wild and no public exploit code.

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

## Sources

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

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