Security readout for executives and security teams
Plain-English summary
This flaw lets an unauthenticated remote attacker bypass SolarWinds Orion API authentication and run API commands. For an affected Orion deployment, that can compromise the monitoring platform and systems it manages. CISA lists CVE-2020-10148 as known exploited, so legacy exposure should be treated as urgent.
Executive priority
Prioritize immediately if any affected Orion version remains deployed or network reachable. This is a critical, known-exploited authentication bypass against a high-value management platform. Leadership should ensure remediation ownership, exposure reduction, and post-remediation review are completed rather than treating this as routine patching.
Technical view
CVE-2020-10148 is a CWE-288 authentication bypass in the SolarWinds Orion API. Affected versions listed are Orion Platform 2019.4 HF 5, 2020.2 without hotfix, and 2020.2 HF 1. CVSS 3.1 is 9.8: network reachable, low complexity, no privileges or user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where affected Orion Platform versions are reachable from the internet, VPN users, partner networks, or broad internal management networks. Because Orion commonly has privileged visibility and integrations, compromise can create wider operational and security impact beyond the Orion server itself.
Exploitation context
Active exploitation is supported by the CISA Known Exploited Vulnerabilities listing. The supplied sources do not provide exploit mechanics, observed campaigns, or detailed indicators. Treat confirmed affected systems as potentially targeted and prioritize containment, upgrade verification, and forensic review.
Researcher notes
The source bundle establishes affected versions, CVSS 9.8, CWE-288, and KEV status. It does not include exact fixed build numbers, exploit request patterns, or vendor detection logic. Validation should focus on version evidence, hotfix confirmation, exposure mapping, and non-invasive log review.
Mitigation direction
- Identify all SolarWinds Orion Platform instances and their exact hotfix levels.
- Follow the SolarWinds security advisory for supported upgrade or hotfix guidance.
- Restrict Orion API access to trusted administrative networks only.
- Review privileged accounts, API integrations, and service credentials tied to Orion.
- Check CISA KEV requirements for remediation timelines in regulated environments.
Validation and detection
- Confirm no instance runs 2019.4 HF 5, 2020.2, or 2020.2 HF 1.
- Verify the applied SolarWinds fix against vendor advisory documentation.
- Review Orion and authentication logs for unexplained API activity.
- Check network exposure from internet, VPN, and internal management segments.
- Document remediation evidence for vulnerability management and audit tracking.
Public sources used
Michael Williams reviewed this cited source version on .
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.
CWE-288: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-10148 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.solarwinds.com/securityadvisoryCVE reference · x_refsource_CONFIRM
- VU#843464CVE reference · third-party-advisory, x_refsource_CERT-VN
- https://www.kb.cert.org/vuls/id/843464CVE reference
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-10148CVE reference · government-resource
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.
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.