CVE-2026-28302: SolarWinds Serv-U Insecure Direct Object Reference (IDOR) Vulnerability
SolarWinds Serv-U is affected by an insecure direct object reference (IDOR) vulnerability that can lead to privilege escalation and remote code execution as root. This issue requires group administrator access. The impact is lower in Windows deployments.
Security readout for executives and security teams
Plain-English summary
A Serv-U group administrator may access an object without proper authorization, potentially escalating privileges and executing code with root authority. Serv-U 15.5.4 HF1 and earlier are affected. The reported impact is lower on Windows, but affected deployments still warrant urgent review.
Executive priority
Treat affected, reachable deployments as an urgent remediation priority, especially on non-Windows systems. Root-level code execution could enable complete server compromise and disruption. Because exploitation requires group administrator access, prioritize systems with exposed administration, weak credential controls, or suspicious administrator activity.
Technical view
CWE-639 IDOR permits a high-privilege, network-based attacker with group administrator access to cross an authorization boundary. The CVSS 3.1 assessment is 9.1: low complexity, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. Successful exploitation can produce root-level remote code execution.
Likely exposure
Exposure requires Serv-U 15.5.4 HF1 or earlier and an attacker-controlled or compromised group administrator account. Network reachability to the relevant management functionality increases practical risk. The supplied evidence does not identify affected configurations beyond product version or quantify internet exposure.
Exploitation context
The vulnerability is not identified as a CISA KEV entry in the supplied bundle, and no cited evidence establishes active exploitation. Exploitation nevertheless requires only group administrator privileges after network access; compromised administrative credentials could therefore turn an existing foothold into full system compromise.
Researcher notes
The supplied record establishes the affected boundary, prerequisite privilege, CWE-639 classification, and potential root RCE. It does not describe the vulnerable object, request flow, platform-specific mechanics, indicators of compromise, or confirmed exploitation. Validation should remain non-invasive and focus on versions, access controls, accounts, and logs.
Mitigation direction
Inventory Serv-U deployments and identify systems running 15.5.4 HF1 or earlier.
Follow SolarWinds guidance and upgrade to a vendor-confirmed unaffected release.
Restrict Serv-U administrative interfaces to trusted networks and authorized administrators.
Review group administrator accounts and remove unnecessary or stale privileges.
Prioritize non-Windows deployments because the reported impact is greater there.
Validation and detection
Confirm the installed Serv-U version and operating system on every deployment.
Verify upgraded systems are outside the vendor-defined affected version range.
Audit group administrator membership for unexpected, shared, or dormant accounts.
Review authentication and administrative activity logs for anomalous group administrator behavior.
Confirm management access is limited by network controls and strong authentication.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.