GHSA-2jvj-mhf2-g99w — silverstripe/framework
MEDIUMGHSA-2jvj-mhf2-g99w is a medium-severity (CVSS 5.5) CWE-74 vulnerability in silverstripe/framework. 2 public exploit references exist, so weaponization risk is real. A fix is available for silverstripe/framework — see the affected versions and patch details below.
SilverStripe CSV Excel Macro Injection
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.
How urgent is this, really
GHSA-2jvj-mhf2-g99w plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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
In the CSV export feature of SilverStripe before 3.5.6, 3.6.x before 3.6.3, and 4.x before 4.0.1, it's possible for the output to contain macros and scripts, which may be executed if imported without sanitization into common software (including Microsoft Excel). For example, the CSV data may contain untrusted user input from the "First Name" field of a user's /myprofile page.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/framework | all versions | 3.5.6composer require silverstripe/framework:^3.5.6 |
| 🐘Packagist | silverstripe/framework | ≥ 3.6.0&&< 3.6.3 | 3.6.3composer require silverstripe/framework:^3.6.3 |
| 🐘Packagist | silverstripe/framework | ≥ 4.0.0&&< 4.0.1 | 4.0.1composer require silverstripe/framework:^4.0.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
SilverStripe CMS 3.6.2 - CSV Excel Macro Injection
by Ishaq Mohammed · Dec 26, 2017
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.5.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jvj-mhf2-g99w 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-2jvj-mhf2-g99w can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2jvj-mhf2-g99w. 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-2jvj-mhf2-g99w in your dependencies?
O3 Security finds GHSA-2jvj-mhf2-g99w across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.