GHSA-2jvj-mhf2-g99w
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. O3 Security confirms whether GHSA-2jvj-mhf2-g99w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
SilverStripe CSV Excel Macro Injection
Blast Radius
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.6 |
| 🐘Packagist | silverstripe/framework | ≥ 3.6.0&&< 3.6.3 | 3.6.3 |
| 🐘Packagist | silverstripe/framework | ≥ 4.0.0&&< 4.0.1 | 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. 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 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 pinpoints whether GHSA-2jvj-mhf2-g99w 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-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 detects GHSA-2jvj-mhf2-g99w across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.