dbcve.org
Serv UApplication · Solarwinds

CVE-2025-40541

HIGH · 7.2 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 15.5.4 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
An Insecure Direct Object Reference (IDOR) vulnerability exists in Serv-U, which when exploited, gives a malicious actor the ability to execute native code as a privileged account. This issue requires administrative privileges to abuse. On Windows deployments, the risk is scored as a medium because services frequently run under less-privileged service accounts by default.

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

This is an IDOR vulnerability in SolarWinds Serv-U file transfer server that allows an authenticated administrator to perform vertical privilege escalation and execute native code as a higher-privileged account. The vulnerability requires the attacker to already possess administrative-level access to the Serv-U instance.

MitigationRestrict administrative access to Serv-U to only necessary trusted personnel, apply vendor patches when available, and on Windows ensure Serv-U runs under a least-privilege service account rather than SYSTEM or high-privilege accounts.

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
Serv UApplication
Affected:< 15.5.4

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

CVSS:3.1/AV:N/AC:L/PR:H/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 Serv-U is installed
    Check for Serv-U installation directory (typically C:\Program Files\SolarWinds\Serv-U on Windows or /opt/Serv-U on Linux) or look for Serv-U processes running (ServUAdmin.exe, ServUDaemon.exe)
    Affected if Serv-U file transfer server is present on the system
  2. Determine installed Serv-U version
    Open Serv-U Administrator console and navigate to Help > About, or check the version in the ServUAdmin.exe file properties, or run: ServUAdmin.exe /version
    Affected if Installed version is lower than 15.5.4 (for example 15.5.3, 15.5.2, 15.4.0, etc.)
  3. Confirm administrative access exists
    Review Serv-U user accounts with Administrative privileges in Serv-U Administrator under Users > select user > Account tab > Administrative Privileges section
    Affected if Any administrative-level account exists in Serv-U configuration (this is the prerequisite for exploitation)

If Serv-U is installed with a version lower than 15.5.4 and administrative accounts are configured, the environment is vulnerable to this IDOR privilege escalation flaw.

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 15.5.4 or later
Fixed in 15.5.4
Interim mitigation

Restrict administrative access to Serv-U to only necessary trusted personnel, apply vendor patches when available, and on Windows ensure Serv-U runs under a least-privilege service account rather than SYSTEM or high-privilege accounts.

Recommended fix Moderate confidence

Serv-U 15.5.4

  1. 1. Back up the current Serv-U configuration and any custom settings
  2. 2. Download Serv-U version 15.5.4 or later from the official SolarWinds download portal
  3. 3. Stop the Serv-U service using the Services console or command line (net stop Serv-U)
  4. 4. Run the Serv-U installer with administrator privileges
  5. 5. Follow the on-screen upgrade prompts, preserving existing configuration when prompted
  6. 6. After installation completes, verify the version number matches 15.5.4 or later
  7. 7. Start the Serv-U service (net start Serv-U)
  8. 8. Confirm normal operation and validate that administrative functions work correctly
Caveat Standard upgrade - review release notes for any configuration or feature changes between your current version and 15.5.4

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

Fix this in Serv U Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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