CVE-2026-28314
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 · uneditedSolarWinds Serv-U is affected by an insecure direct object reference vulnerability that leads to an account takeover. User authentication is required. The impact is lower in Windows deployments.
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 confidenceSolarWinds Serv-U contains an Insecure Direct Object Reference (IDOR) vulnerability that allows authenticated users to access or modify unauthorized resources, enabling account takeover. The vulnerability exists in the authorization mechanism where object references are not properly validated against the current user's permissions.
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< 2026.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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.
-
Identify if SolarWinds Serv-U is installedLocate Serv-U installation directories or check installed programs list for 'Serv-U' or 'SolarWinds Serv-U'Affected if Serv-U is present on the system
-
Determine the installed Serv-U versionAccess the Serv-U admin console or use the built-in version check command (typically available via admin interface or help/about section)Affected if The installed version is any version prior to 2026.3
-
Verify if user management functionality is accessibleCheck if the Serv-U web admin console or API includes user management endpoints (such as user listing, user creation, or user modification interfaces)Affected if User management features are enabled and accessible to non-administrator authenticated users
-
Confirm multi-user configuration existsReview user accounts in Serv-U to determine if more than one user account is configured beyond the default administratorAffected if Multiple user accounts exist in the Serv-U environment
-
Check for authorization controls on user operationsExamine the Serv-U configuration or user role settings to determine if there are role-based access controls restricting users to only their own account dataAffected if Users with standard (non-administrator) roles can potentially reference other user IDs in API requests or web forms without receiving an authorization error
A system is affected if SolarWinds Serv-U version is below 2026.3 and the environment contains multiple user accounts with standard authenticated access to user management functionality.
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.
From vendor data2026.3
Apply vendor-provided patches or update to the latest version of Serv-U; implement proper authorization checks on all object references and validate user permissions before granting access to sensitive resources.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28314 — 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-2026-28314 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