GHSA-fmg2-f5r9-24qc — getgrav/grav
Fix: getgrav/grav-plugin-admin@f67cc18GHSA-fmg2-f5r9-24qc is a Cross-site Scripting (XSS) vulnerability in getgrav/grav. A fix is available for getgrav/grav — see the affected versions and patch details below.
Grav: Stored XSS via page title (data[header][title]) in admin panel
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
getgrav/gravReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A Stored Cross-Site Scripting (XSS) vulnerability was identified in the /admin/pages/[page] endpoint of the Grav application. This vulnerability allows attackers to inject malicious scripts into the data[header][title] parameter.
Details
Vulnerable Endpoint: GET /admin/pages/[page] Parameter: data[header][title]
The application fails to properly validate and sanitize user input in the data[header][title] parameter. As a result, attackers can craft a malicious URL with an XSS payload. When this URL is accessed, the injected script is reflected back in the HTTP response and executed within the context of the victim's browser session.
PoC
Payload: <img src=1 onerror=alert(1)>
-
Log in to the Grav Admin Panel and navigate to Pages.
-
Create a new page or edit an existing one.
-
Edit title of the page to
<img src=1 onerror=alert(1)>
-
Save page
-
Open the move function and click on the folder having the payload
Impact
Stored 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 Vu Duc Hieu Contributor Simon Tran
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | getgrav/grav | all versions | 1.7.49.5composer require getgrav/grav:^1.7.49.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getgrav/grav, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update getgrav/grav to 1.7.49.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fmg2-f5r9-24qc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fmg2-f5r9-24qc can be triaged on real exposure rather than presence alone.
Tailored to GHSA-fmg2-f5r9-24qc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-fmg2-f5r9-24qc in your dependencies?
O3 Security finds GHSA-fmg2-f5r9-24qc across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.