CVE-2019-1010199 json
Cross site scripting attack in ServiceStack Framework
published 7y ago modified 4mo ago also GHSA-vcfc-9wcp-j623 , EUVD-2022-5338
- cvss
- 6.1
- 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
ServiceStack ServiceStack Framework 4.5.14 is affected by: Cross Site Scripting (XSS). The impact is: JavaScrpit is reflected in the server response, hence executed by the browser. The component is: the query used in the GET request is prone. The attack vector is: Since there is no server-side validation and If Browser encoding is bypassed, the victim is affected when opening a crafted URL. The fixed version is: 5.2.0.
Patch / fix
Is CVE-2019-1010199 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.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/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.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | ServiceStack | >=4.5.14, <5.2.0 |
5.2.0 |
Affected products
- ServiceStack ServiceStack Framework
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/ServiceStack/ServiceStack/commit/a0e0d7de20f5d1712f1793f925496def4383c610
web, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-1010199
advisory
-
github.com
/ServiceStack/ServiceStack
package
Sources
- CVE List CVE-2019-1010199
- GitHub Advisory GHSA-vcfc-9wcp-j623
- NVD CVE-2019-1010199
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.