CVE-2021-38168
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 authenticated SQL injection via select_servers.
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 versions through 5.2.2.0 contain an authenticated SQL injection vulnerability in the select_servers parameter. An authenticated attacker can inject malicious SQL queries through this parameter to manipulate database queries, potentially allowing data exfiltration, modification, or administrative access.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Roxy-WI installationLocate Roxy-WI by checking common installation directories (such as /opt/roxy-wi, /usr/local/roxy-wi, or the web server root), or by searching for roxy-wi related files using: find / -name '*roxy*' -type f 2>/dev/null | head -20Affected if Roxy-WI software is found on the system
-
Determine installed Roxy-WI versionCheck the version by inspecting the web interface footer, looking for a version file (often named version, ver, or similar in the installation directory), or checking package information if installed via a package managerAffected if The installed version is 5.2.2.0 or any version lower (e.g., 5.2.1.0, 5.1.x, 5.0.x)
-
Verify authentication is enabled for the select_servers functionExamine the web application's authentication configuration and determine if the select_servers parameter endpoint is accessible to authenticated users. Check application logs or configuration files for role-based access settings related to server selection featuresAffected if The select_servers parameter endpoint is accessible without additional authentication barriers beyond basic user login
-
Review database query logs for anomaliesExamine database logs (MySQL, PostgreSQL, or SQLite depending on configuration) for unusual or suspicious SQL queries, especially those containing string literals, comments (--, /* */), or UNION statements in the select_servers contextAffected if Unexpected SQL patterns or injection attempts appear in database query logs
-
Check web application logs for exploitation attemptsReview web server access logs (typically in /var/log/httpd, /var/log/nginx, or within the Roxy-WI logs directory) for requests to endpoints handling the select_servers parameter with unusual payloadsAffected if Requests containing SQL injection patterns (quotes, UNION, comment symbols) in select_servers parameter are found in logs
A system is affected if Roxy-WI version 5.2.2.0 or lower is installed and the select_servers functionality is accessible to authenticated users, warranting further investigation for indicators of compromise.
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 dataRemediate by implementing parameterized queries or prepared statements for all database operations involving user input, specifically the select_servers parameter. Apply input validation and least-privilege database accounts to limit impact.
- 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-38168 — 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-38168 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