GHSA-r9vp-fp72-xgf7 is a medium-severity (CVSS 5.4) vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.
silverstripe/framework's `Member.Name` is not escaped
Real-World Exposure
silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/frameworkReal-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
The core template framework/templates/Includes/GridField_print.ss uses "Printed by $Member.Name".
If the currently logged in members first name or surname contain XSS, this prints the raw HTML out, because Member->getName() just returns the raw FirstName + Surname as a string, which is injected directly.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/framework | ≥ 3.1.9-rc1&&< 3.1.20 | 3.1.20composer require silverstripe/framework:^3.1.20 |
| 🐘Packagist | silverstripe/framework | ≥ 3.2.4-rc1&&< 3.2.5 | 3.2.5composer require silverstripe/framework:^3.2.5 |
| 🐘Packagist | silverstripe/framework | ≥ 3.3.2-rc1&&< 3.3.3 | 3.3.3composer require silverstripe/framework:^3.3.3 |
| 🐘Packagist | silverstripe/framework | ≥ 3.4.0-rc1&&< 3.4.1 | 3.4.1composer require silverstripe/framework:^3.4.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/framework to 3.1.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9vp-fp72-xgf7 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-r9vp-fp72-xgf7 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r9vp-fp72-xgf7. 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-r9vp-fp72-xgf7 in your dependencies?
O3 Security finds GHSA-r9vp-fp72-xgf7 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.