Security readout for executives and security teams
Plain-English summary
ServiceStack Framework 4.5.14 can reflect JavaScript from a GET query back into a page, allowing browser execution if a victim opens a crafted URL and browser encoding protections are bypassed. The source names version 5.2.0 as fixed.
Executive priority
Treat this as a targeted remediation item, not an emergency based on available evidence. Prioritize internet-facing ServiceStack 4.5.14 applications, because reflected XSS can affect users through malicious links even when server compromise is not indicated.
Technical view
The CVE describes reflected XSS in the query used by a GET request, caused by missing server-side validation. Affected scope is ServiceStack Framework 4.5.14, with a fix identified in 5.2.0. No CVSS, CWE, or detailed affected endpoint list is provided.
Likely exposure
Exposure is most likely in applications running ServiceStack Framework 4.5.14, especially public-facing routes that reflect query input in browser-rendered responses. Systems already upgraded to 5.2.0 or later are not identified as affected in the bundle.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. The described attack depends on a victim opening a crafted URL and browser-side execution occurring after encoding protections are bypassed.
Researcher notes
Evidence is limited to the CVE description and linked ServiceStack commit. The record does not provide CVSS, CWE mapping, endpoint details, or exploitation evidence. Avoid broad claims beyond ServiceStack Framework 4.5.14 fixed in 5.2.0.
Mitigation direction
- Inventory applications using ServiceStack Framework and identify version 4.5.14.
- Upgrade affected applications to ServiceStack Framework 5.2.0 or later.
- Review the linked ServiceStack commit and vendor guidance for implementation details.
- Verify server-side validation and output encoding on query-reflecting routes.
- Prioritize public-facing applications and authenticated portals with user traffic.
Validation and detection
- Confirm deployed ServiceStack package versions across production and staging.
- Review GET handlers for reflected query values in HTML responses.
- Check whether affected applications include the vendor fix from version 5.2.0.
- Run approved XSS regression tests against representative routes.
- Review access logs for unusual crafted query URLs without attempting exploitation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-1010199 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ServiceStack/ServiceStack/commit/a0e0d7de20f5d1712f1793f925496def4383c610CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.