CVE-2021-38167
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 · uneditedRoxy-WI through 5.2.2.0 allows SQL Injection via check_login. An unauthenticated attacker can extract a valid uuid to bypass authentication.
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 confidenceRoxy-WI through version 5.2.2.0 contains a SQL Injection vulnerability in the check_login function. An unauthenticated attacker can exploit this to inject SQL queries and extract a valid UUID, allowing them to bypass authentication and gain unauthorized access to the application.
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<= 5.2.2.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify installed Roxy-WI versionLocate the Roxy-WI installation and retrieve its version number from the software, typically found in the web interface footer, an about page, or version configuration fileAffected if The installed version is 5.2.2.0 or any lower version (any release <= 5.2.2.0)
-
Verify login interface accessibilityConfirm that the Roxy-WI web interface login page is exposed on the network, typically on port 80 or 443Affected if The login interface is reachable from a network where untrusted users could attempt exploitation
-
Confirm check_login function is presentExamine the Roxy-WI source code or application files to locate the check_login function that handles authentication logicAffected if The check_login function exists in the codebase and handles user authentication without proper SQL injection protection
-
Test for SQL injection vulnerabilitySubmit crafted input in the login username/password fields that contains SQL metacharacters (such as quotes or SQL-specific keywords) to observe if the application returns SQL error messages or exhibits unexpected behaviorAffected if The application returns database error messages, executes injected SQL queries, or allows authentication bypass when special SQL characters are submitted
A user is affected if their Roxy-WI installation is version 5.2.2.0 or lower AND the login interface is network-accessible to untrusted users, as the check_login function contains exploitable SQL injection that can allow authentication bypass.
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 dataUpgrade to a patched version of Roxy-WI. If no patch is available, temporarily restrict network access to the login interface while implementing input validation and parameterized queries to remediate the SQL injection.
- 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-2021-38167 — 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-38167 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