CVE-2021-28157
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 · uneditedAn SQL Injection issue in Devolutions Server before 2021.1 and Devolutions Server LTS before 2020.3.18 allows an administrative user to execute arbitrary SQL commands via a username in api/security/userinfo/delete.
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 confidenceSQL injection vulnerability in Devolutions Server's api/security/userinfo/delete endpoint allows authenticated administrative users to execute arbitrary SQL commands through the username parameter. Affects versions prior to 2011.1 and LTS versions before 2020.3.18.
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< 2020.3.18< 2021.1CVSS 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.
-
Confirm Devolutions Server installationLocate the Devolutions Server installation directory or check installed programs on the Windows system where it may be hosted. Common paths include C:\Program Files\Devolutions\Server or check Services for 'Devolutions Server'Affected if Devolutions Server is not installed on the system
-
Identify installed versionCheck the version of Devolutions Server by inspecting the application itself, configuration files, or the Windows installed programs list. The version is typically displayed in the server's web interface or in installation metadataAffected if The installed version cannot be determined or is not visible
-
Compare version to affected rangesCompare your installed version number against the affected ranges: versions prior to 2021.1, or LTS versions prior to 2020.3.18. If you are on an LTS track, verify the specific LTS version numberAffected if Installed version is below 2021.1 or below 2020.3.18 (for LTS)
-
Verify API accessibilityConfirm the api/security/userinfo/delete endpoint is accessible on your Devolutions Server instance. This requires authentication as an administrative user to interact with this API endpointAffected if The endpoint exists and responds to requests in the affected version
You are affected if Devolutions Server is installed and the version is below 2021.1 or below 2020.3.18 for LTS versions.
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 data2020.3.182021.1
Upgrade Devolutions Server to version 2011.1 or later (or LTS 2020.3.18 or later), and implement parameterized queries to prevent SQL injection in the affected endpoint.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28157 — 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-2021-28157 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