NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

SilverStripe CSV Excel Macro InjectionGHSA-2jvj-mhf2-g99w

MEDIUM

GHSA-2jvj-mhf2-g99w is a medium-severity (CVSS 5.5) CWE-74 vulnerability in silverstripe/framework. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for silverstripe/framework — see the affected versions and patch details below.

Also known asCVE-2017-18049
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
2 known
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.47%0.94%1.42%0.2%0.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework

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

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

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsilverstripe/frameworkall versions3.5.6composer require silverstripe/framework:^3.5.6
🐘Packagistsilverstripe/framework≥ 3.6.0&&< 3.6.33.6.3composer require silverstripe/framework:^3.6.3
🐘Packagistsilverstripe/framework≥ 4.0.0&&< 4.0.14.0.1composer require silverstripe/framework:^4.0.1

Affected Products

1 product · 3 configurations
Application
silverstripesilverstripe
≥ 3.6.0 && ≤ 3.6.2
1 version
4.0.0
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-43396webappsphp✓ Verified

SilverStripe CMS 3.6.2 - CSV Excel Macro Injection

by Ishaq Mohammed · Dec 26, 2017

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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.

  3. 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.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-2jvj-mhf2-g99w in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
SilverStripe CSV Excel Macro Injection (Medium 5.5)