dbcve.org
Solarwinds PlatformApplication · Solarwinds

CVE-2023-50395

HIGH · 8.0 CVSS v3.1 Published 2024-02-06
Fix available
A fix is available. Upgrade to 2024.1 or later.
See remediation →
82/100
Remediation priority · High
Zero-click

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 · unedited
SQL Injection Remote Code Execution Vulnerability was found using an update statement in the SolarWinds Platform. This vulnerability requires user authentication to be exploited

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 confidence

A SQL injection vulnerability in the SolarWinds Platform's update statement allows authenticated attackers to execute arbitrary code. This high-severity (CVSS 8) flaw exploits unsanitized input in database update operations, potentially allowing complete system compromise.

MitigationApply the SolarWinds vendor patch immediately. Since authentication is required, enforce least-privilege access to affected components and monitor for anomalous database queries as a defense-in-depth measure while patching.

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
Solarwinds PlatformApplication
Affected:< 2024.1

CVSS 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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SolarWinds Platform is installed
    Check the installed software inventory or look for SolarWinds Platform processes/services running on the system
    Affected if SolarWinds Platform software is present on the system
  2. Determine the installed SolarWinds Platform version
    Use the SolarWinds Platform's built-in version check (typically via the Orion Diagnostic Manager or the About section in the management console), or check the installer version if accessible
    Affected if The installed version is any version prior to 2024.1 (e.g., 2023.x, 2022.x, earlier releases)
  3. Verify if the Orion Database Manager or related database update features are in use
    Check if the SolarWinds Platform database configuration is active and if the Orion Update Manager or similar database-facing components are enabled in the platform settings
    Affected if Database update functionality is enabled and the platform is operational
  4. Confirm network accessibility of the SolarWinds web console
    Determine if the SolarWinds Platform web interface (Orion) is exposed to the network or accessible remotely, as authentication is required to exploit the vulnerability
    Affected if The SolarWinds web console is accessible over the network and user accounts exist in the system
  5. Review user account configuration
    Check if there are any user accounts configured in SolarWinds Platform beyond the default administrator, particularly service accounts or low-privilege users that could be leveraged for authentication-based exploitation
    Affected if There are authenticated user accounts configured in the platform beyond the initial setup

A system is affected if SolarWinds Platform is installed with a version prior to 2024.1 and has active user accounts that can authenticate to the platform's database update functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2024.1 or later
Fixed in 2024.1
Interim mitigation

Apply the SolarWinds vendor patch immediately. Since authentication is required, enforce least-privilege access to affected components and monitor for anomalous database queries as a defense-in-depth measure while patching.

Recommended fix High confidence

SolarWinds Platform 2024.1 or later

  1. 1. Backup the current SolarWinds Platform configuration and database
  2. 2. Review the SolarWinds Platform 2024.1 release notes for any prerequisites
  3. 3. Download the SolarWinds Platform 2024.1 (or latest available) installer from the official SolarWinds customer portal
  4. 4. Ensure all users are logged out of the platform before beginning the upgrade
  5. 5. Run the installer and follow the on-screen upgrade wizard instructions
  6. 6. After upgrade completes, verify the SolarWinds Platform services are running
  7. 7. Log in and confirm the SQL injection vulnerability is remediated by verifying the affected update statement functionality works correctly with proper input validation
Caveat Review 2024.1 release notes for any configuration changes or deprecated features before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solarwinds Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50395 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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