CVE-2019-19325 json
Reflected XSS in SilverStripe
published 6y ago modified 4mo ago also GHSA-qvrv-2x7x-78x2 , EUVD-2020-0310
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
SilverStripe through 4.4.x before 4.4.5 and 4.5.x before 4.5.2 allows Reflected XSS on the login form and custom forms. Silverstripe Forms allow malicious HTML or JavaScript to be inserted through non-scalar FormField attributes, which allows performing XSS (Cross-Site Scripting) on some forms built with user input (Request data). This can lead to phishing attempts to obtain a user's credentials or other sensitive user input.
Patch / fix
- packagist silverstripe/framework 4.4.5, 4.5.2
- silverstripe silverstripe 4.4.5, 4.5.2
Is CVE-2019-19325 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.69% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 |
|---|---|---|---|
| packagist | silverstripe/framework | >=4.5.0, <4.5.2 >=4.0.0, <4.4.5 |
4.5.2 4.4.5 |
Classification
References
-
github.com
/silverstripe/silverstripe-framework/commit/49fda52b12ba59f0a04bcabf78425586a8779e89
web
-
silverstripe.org
/download/security-releases/cve-2019-19325
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-19325
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2019-19325.yaml
web
Sources
- CVE List CVE-2019-19325
- GitHub Advisory GHSA-qvrv-2x7x-78x2
- NVD CVE-2019-19325
Fencer Intel 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.