CVE-2025-40538
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 broken access control vulnerability exists in Serv-U which when exploited, gives a malicious actor the ability to create a system admin user and execute arbitrary code as a privileged account via domain admin or group admin privileges. 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 · high confidenceThis is a broken access control vulnerability in SolarWinds Serv-U file transfer server. An authenticated attacker with domain admin or group admin privileges can create unauthorized system admin users and execute arbitrary code with elevated privileges. The vulnerability requires administrative access to exploit, limiting the attack surface but still allowing significant privilege escalation.
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< 15.5.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Serv-U versionOpen Serv-U Administration console, go to Help > About, or check Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\SolarWinds\Serv-U\VersionAffected if Version is lower than 15.5.4 (for example, 15.5.3, 15.5.2, etc.)
-
Review Serv-U admin usersIn Serv-U Administration console, navigate to Users > System Administration > Administrators. Inspect the list of system admin accounts for any unauthorized or unexpected entriesAffected if There are admin accounts that were not created by known, authorized administrators
-
Check Windows security event logsOpen Windows Event Viewer, navigate to Security events. Look for Event ID 4720 (user account created) or 4726 (user account deleted) targeting Serv-U service accounts or domain admin-equivalent accountsAffected if Admin user creation events exist that were not initiated by documented, legitimate administrator actions
-
Examine Serv-U audit logs for privilege changesIn Serv-U Administration console, go to Logging > View Logs. Filter for events related to adding administrators or changing admin privilegesAffected if Audit logs show admin account creation or privilege escalation events not matching known administrative procedures
You are affected if running Serv-U version 15.5.3 or earlier AND you discover unauthorized system admin users in Serv-U or unexpected admin creation events in logs.
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.
dbcve · scoped15.5.4
Apply the vendor-supplied patch when available. Until then, restrict administrative access to Serv-U, monitor for unauthorized admin user creation, and ensure Serv-U runs under a least-privilege service account on Windows deployments.
Serv-U 15.5.4
- 1. Back up the current Serv-U configuration and all user data
- 2. Download Serv-U version 15.5.4 or later from the official SolarWinds download portal
- 3. Apply the upgrade to Serv-U following the standard upgrade procedure documented at documentation.solarwinds.com
- 4. After upgrade, verify the Serv-U service is running correctly
- 5. Confirm the vulnerability is remediated by verifying that domain admin or group admin accounts can no longer create system admin users or execute arbitrary code with elevated privileges
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40538 — 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-2025-40538 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