Summary
Grav is vulnerable to Cross-Site Scripting (XSS) Reflected endpoint /admin/pages/[page], parameter data[header][content][items], located in the "Blog Config" tab
Impact
Reflected cross-site scripting (XSS) attacks can have serious consequences, including:
User actions: Attackers can perform actions on behalf of the user
Data theft: Sensitive information such as session cookies can be stolen
Account compromise: Attackers may impersonate legitimate users
Malicious code execution: Arbitrary JavaScript code can run in the user’s browser
Website defacement or misinformation: Malicious output may be injected visually
User redirection: Victims may be redirected to phishing or malicious websites
by CVE-Hunters
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-66309? CVE-2025-66309 is a medium-severity cross-site scripting (XSS) vulnerability in getgrav/grav (composer), affecting versions < 1.8.0-beta.27. It is fixed in 1.8.0-beta.27. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of getgrav/grav are affected by CVE-2025-66309? getgrav/grav (composer) versions < 1.8.0-beta.27 is affected.
- Is there a fix for CVE-2025-66309? Yes. CVE-2025-66309 is fixed in 1.8.0-beta.27. Upgrade to this version or later.
- Is CVE-2025-66309 exploitable, and should I be worried? Whether CVE-2025-66309 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-66309 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-66309? Upgrade
getgrav/gravto 1.8.0-beta.27 or later.