CVE-2017-18049 json
SilverStripe CSV Excel Macro Injection
published 2018-01-23 8 y ago modified 2026-06-17 4 mo ago also GHSA-2jvj-mhf2-g99w , EUVD-2022-2006
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist silverstripe/framework 3.5.6, 3.6.3, 4.0.1
Exploit prediction
0.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- exploit-db.com https://www.exploit-db.com/exploits/43396/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | <3.5.6 >=3.6.0, <3.6.3 >=4.0.0, <4.0.1 |
3.5.6 3.6.3 4.0.1 |
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
References
-
exploit-db.com
/exploits/43396/
exploit, third-party-advisory, vdb-entry
-
silverstripe.org
/download/security-releases/ss-2017-007
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-18049
advisory
-
github.com
/silverstripe/silverstripe-framework
package
-
exploit-db.com
/exploits/43396
web
Sources
- CVE List CVE-2017-18049
- GitHub Advisory GHSA-2jvj-mhf2-g99w
- NVD CVE-2017-18049
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.