CVE-2025-66312 — getgrav/grav
Fix: getgrav/grav-plugin-admin@99f6532CVE-2025-66312 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 Admin Plugin vulnerable to Cross-Site Scripting (XSS) Stored endpoint `/admin/accounts/groups/[group]` parameter `data[readableName]`
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-66312.
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/accounts/groups/Grupo endpoint of the Grav application. This vulnerability allows attackers to inject malicious scripts into the data[readableName] parameter. The injected scripts are stored on the server and executed automatically whenever the affected page is accessed by users, posing a significant security risk.
Details
Vulnerable Endpoint: POST /admin/accounts/groups/Grupo
Parameter: data[readableName]
The application fails to properly validate and sanitize user input in the data[readableName] parameter. This lack of input handling allows attackers to inject arbitrary script content that is stored in the application and executed in the browser of any user who views the affected group configuration.
PoC
Payload:
<ScRipT>alert('PoC-XSS')</ScRipT>
-
Navigate to Accounts > Groups in the administrative panel.
-
Create a new group or edit an existing one.
-
In the Display Name field (
data[readableName]), insert the payload above and save the changes.
The following HTTP request was generated during this action:
- Next, go to Accounts > Users and open any user profile.
- The malicious script is executed immediately in the browser when the page loads, confirming the existence of a Stored XSS vulnerability.
Impact
Stored XSS vulnerabilities can result in serious consequences, including:
-
Session hijacking: Attackers can steal authentication cookies or tokens
-
Malware delivery: Inserting scripts that download malicious content
-
Credential theft: Capturing usernames and passwords through injected forms
-
Sensitive data exposure: Accessing data stored in the browser or the application
-
Browser takeover: Executing arbitrary commands in the user’s session
-
Phishing attacks: Redirecting users to fake login or malicious sites
-
Website defacement: Altering page content shown to users
-
Reputational damage: Undermining trust in the platform or organization
by CVE-Hunters
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | getgrav/grav | all versions | 1.8.0-beta.27composer require getgrav/grav:^1.8.0-beta.27 |
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.8.0-beta.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-66312 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 CVE-2025-66312 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-66312. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-66312 in your dependencies?
O3 Security finds CVE-2025-66312 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.