dbcve.org
Solarwinds PlatformApplication · Solarwinds

CVE-2023-35188

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 a create 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

SQL injection vulnerability in SolarWinds Platform allows authenticated users to execute arbitrary SQL statements through CREATE statements, potentially achieving remote code execution. The vulnerability exists in the platform's database interaction layer where user-supplied input is not properly sanitized before being used in SQL queries.

MitigationApply available vendor patches for SolarWinds Platform immediately. Until patches are available, restrict administrative access to trusted personnel only and monitor database query logs for anomalous CREATE statement activity.

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 the installed SolarWinds Platform version
    Access the SolarWinds Platform web interface and navigate to the About or Settings section to view the version number, or use the SolarWinds Configuration Wizard to confirm the installed version.
    Affected if The installed version is any release prior to 2024.1
  2. Verify database interaction features are enabled
    Review the SolarWinds Platform configuration settings related to database connectivity and custom query features. Check if the database interaction layer is accessible through the admin interface or API endpoints.
    Affected if Database interaction features or custom query capabilities are enabled in the platform
  3. Review database query logs for anomalous CREATE statements
    Examine the SolarWinds Platform database logs and any associated database audit logs. Look for CREATE statements that originate from user sessions, especially those with unusual table or object names.
    Affected if Logs contain CREATE statements from user accounts that were not explicitly authorized or expected

If the installed version is before 2024.1 and the database interaction layer is accessible, the environment may be vulnerable to SQL injection through CREATE statements.

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 available vendor patches for SolarWinds Platform immediately. Until patches are available, restrict administrative access to trusted personnel only and monitor database query logs for anomalous CREATE statement activity.

Recommended fix High confidence

SolarWinds Platform 2024.1

  1. Verify current SolarWinds Platform version by navigating to Settings > About in the web interface
  2. Download the SolarWinds Platform 2024.1 installer from the official SolarWinds customer portal at https://customerportal.solarwinds.com
  3. Review the SolarWinds Platform upgrade guide and release notes for 2024.1
  4. Create a full backup of the SolarWinds database and configuration files
  5. Schedule a maintenance window as upgrades may require downtime
  6. Stop all SolarWinds services before beginning the upgrade
  7. Run the installer with administrative privileges
  8. Follow the on-screen installation wizard prompts

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

Fix this in Solarwinds Platform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35188 — 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-35188 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