CVE-2019-17125
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 Reflected Client Side Template Injection (CSTI) with Angular was discovered in the SolarWinds Orion Platform 2019.2 HF1 in many forms. An attacker can inject an Angular expression and escape the Angular sandbox to achieve stored XSS.
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 · high confidenceReflected Client-Side Template Injection (CSTI) vulnerability in SolarWinds Orion Platform 2019.2 HF1 allows attackers to inject malicious Angular template expressions that escape the Angular sandbox, leading to stored Cross-Site Scripting (XSS). This occurs due to insufficient sanitization of user-supplied input in multiple form fields.
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.
-
Verify SolarWinds Orion Platform versionLog into the Orion web console and navigate to the About or Support page to view the installed version. Alternatively, check the installation directory for version metadata or use the Orion Configuration Wizard.Affected if The installed version is exactly 2019.2
-
Confirm the platform is running the HF1 hotfixCheck the Orion Platform build number or hotfix information in the Support or System Summary page. The vulnerability specifically affects 2019.2 HF1.Affected if The build corresponds to the 2019.2 HF1 release
-
Identify accessible user input form fieldsReview the Orion web interface for form fields that accept user-supplied input, particularly in areas where data can be saved and displayed back to users or administrators.Affected if The environment contains form fields that handle user-supplied data and are accessible without authentication or with low-privilege access
-
Test for Angular sandbox escapeSubmit a known Angular template injection payload such as {{constructor.constructor('alert(1)')()}} into identified form fields. If the expression executes rather than being rendered as plain text, the vulnerability is present.Affected if Angular template expressions render and execute instead of being sanitized and displayed as text
-
Check for stored XSS indicatorsReview application logs and examine saved form submissions to determine if injected template expressions have been stored and are being rendered to other users.Affected if Injected template expressions are stored and rendered to users without sanitization
You are affected if your SolarWinds Orion Platform installation is version 2019.2 HF1 and user-supplied input in form fields can trigger Angular template expression execution.
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 dataApply the vendor-supplied patch or upgrade to a patched version of SolarWinds Orion Platform. Implement additional input validation and output encoding on all form fields to prevent Angular template injection.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17125 — 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-17125 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