# CVE-2025-64059: Cross-site scripting in Grav

> Administrators can inject JavaScript via the Home Page editor, potentially leading to stored XSS, though relevance is disputed due to existing admin privileges.

- **Severity:** Low 1.8 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-2x7f-7273-jx2j

## What is CVE-2025-64059?

CVE-2025-64059 is a low-severity cross-site scripting vulnerability in getgrav Grav, published on 13 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Grav 1.7.50.2 allows admins to enter JavaScript via the Home Page editor. NOTE: the relevance of this for stored XSS is disputed because admins are allowed to modify templates, install plugins, and upload other executable content.

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

## Which versions are affected by CVE-2025-64059?


## How do I fix CVE-2025-64059?

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

## Is CVE-2025-64059 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64059 and fix it if it is affected.

What it is: CVE-2025-64059 is a low-severity cross-site scripting vulnerability in getgrav Grav, published on 13 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64059 exists.

Affected product: getgrav Grav. 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-2025-64059/ (Markdown: https://insights.sbomify.com/CVE-2025-64059/index.md)
```

## Sources

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

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