MediumGHSA-2jvj-mhf2-g99wCVE-2017-18049
SilverStripe CSV Excel Macro Injection
Published 14 May 2022 · Updated 25 Apr 2024
Affected packages
silverstripe/frameworkComposer
- Affected
- <3.5.6
- Fixed in
- 3.5.6
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.5.6silverstripe/frameworkComposer
- Affected
- >=3.6.0 <3.6.3
- Fixed in
- 3.6.3
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.6.3silverstripe/frameworkComposer
- Affected
- >=4.0.0 <4.0.1
- Fixed in
- 4.0.1
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^4.0.1Details
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.
Is GHSA-2jvj-mhf2-g99w in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected silverstripe/framework, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.