CVE-2017-16009 json
XSS via Angular Expression in ag-grid
published 2018-06-04 8 y ago modified 2026-06-17 4 mo ago also GHSA-wfw3-rgfr-6g67 , EUVD-2020-1346
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
ag-grid is an advanced data grid that is library agnostic. ag-grid is vulnerable to Cross-site Scripting (XSS) via Angular Expressions, if AngularJS is used in combination with ag-grid.
Patch / fix
- ag-grid ag-grid 27.0.0
Exploit prediction
1.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- spring.io https://spring.io/blog/2016/01/28/angularjs-escaping-the-expression-sandbox-for-xss referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | ag-grid | <=18.1.3-beta.1 |
no fix listed |
Affected products
- HackerOne ag-grid node module
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
spring.io
/blog/2016/01/28/angularjs-escaping-the-expression-sandbox-for-xss
web, exploit, technical-description, third-party-advisory
-
nodesecurity.io
/advisories/327
broken-link, third-party-advisory
-
github.com
/ceolter/ag-grid/issues/1287
web, issue-tracking, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-16009
advisory
-
github.com
/ag-grid/ag-grid
package
Sources
- CVE List CVE-2017-16009
- GitHub Advisory GHSA-wfw3-rgfr-6g67
- NVD CVE-2017-16009
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.