How severe is GHSA-rmw5-f87r-w988?

No CVSS score has been assigned to GHSA-rmw5-f87r-w988 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rmw5-f87r-w988?

GHSA-rmw5-f87r-w988 affects the following packages: getgrav/grav (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rmw5-f87r-w988?

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 GHSA-rmw5-f87r-w988 is resolved across your whole dependency graph.

How do I detect GHSA-rmw5-f87r-w988 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getgrav/grav. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rmw5-f87r-w988 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-rmw5-f87r-w988?

O3 pinpoints whether GHSA-rmw5-f87r-w988 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rmw5-f87r-w988 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rmw5-f87r-w988 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-rmw5-f87r-w988?

GHSA-rmw5-f87r-w988 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-rmw5-f87r-w988 published, and has it been updated?

GHSA-rmw5-f87r-w988 was published on December 2, 2025 and was last updated on December 2, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-rmw5-f87r-w988

Fix: getgrav/grav-plugin-admin@99f6532

GHSA-rmw5-f87r-w988 is a Cross-site Scripting (XSS) vulnerability in getgrav/grav. O3 Security confirms whether GHSA-rmw5-f87r-w988 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Grav Admin Plugin is vulnerable to Cross-Site Scripting (XSS) Stored endpoint `/admin/accounts/groups/[group]` parameter `data[readableName]`

Also known asCVE-2025-66312

Published

Dec 2, 2025

Updated

Dec 2, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘getgrav/grav

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`getgrav/grav`	all versions	1.8.0-beta.27

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getgrav/grav. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-rmw5-f87r-w988 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 pinpoints whether GHSA-rmw5-f87r-w988 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rmw5-f87r-w988. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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 i

O3 Security · Impact-Aware SCA

Is GHSA-rmw5-f87r-w988 in your dependencies?

O3 detects GHSA-rmw5-f87r-w988 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works