CVE-2019-17127
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Stored Client Side Template Injection (CSTI) with Angular was discovered in the SolarWinds Orion Platform 2019.2 HF1 in many application forms. An attacker can inject an Angular expression and escape the Angular sandbox to achieve stored XSS. This can lead to privilege escalation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stored Client-Side Template Injection (CSTI) vulnerability in SolarWinds Orion Platform 2019.2 HF1 allows attackers to inject Angular expressions that escape the Angular sandbox, achieving stored XSS. This affects multiple application forms and can lead to privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2019.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed SolarWinds Orion Platform versionAccess the Orion web interface and navigate to the About or Help section, or check the installer/API: GET /Orion/About.aspx or check the registry on the server for the version keyAffected if The version is exactly 2019.2 (any HF1 build within 2019.2)
-
Confirm the application is using Angular frameworkInspect the page source of any Orion web page and look for AngularJS or Angular script references, or check the resources loaded in the browser DevTools Network tabAffected if Angular is present in the web interface (required for the sandbox escape to apply)
-
Identify if vulnerable forms are accessibleCheck if the application exposes user-facing forms such as the Alerting, Reporting, or User Management interfaces. These are documented as affected areas for the stored CSTIAffected if Any of the affected forms (multiple application forms as noted in the CVE) are accessible to low-privilege users or untrusted input
-
Test for Angular sandbox escape capabilityIn a form field that accepts user input, attempt to inject a known Angular sandbox escape payload such as {{constructor.constructor('alert(1)')()}} and observe if it executesAffected if The injected Angular expression executes as JavaScript, indicating the sandbox escape is present and the stored XSS is exploitable
-
Review application logs for injection attemptsCheck Orion logs in the SolarWinds directory for entries containing template syntax or Angular expressions in input fieldsAffected if Logs show unescaped Angular template syntax being stored or processed by the application
A system is affected if it runs SolarWinds Orion Platform version 2019.2 and the Angular-based web interface processes unsanitized template expressions in user-accessible forms, enabling stored XSS via sandbox escape.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of SolarWinds Orion Platform or implement proper input sanitization/escaping for Angular template expressions to prevent sandbox escape.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-17127 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data