CVE-2026-57517
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 · uneditedControl Web Panel before 0.9.8.1225 contains a blind SQL injection vulnerability that allows unauthenticated remote attackers to execute arbitrary SQL queries by submitting unsanitized input through the userRes POST parameter at the user endpoint. Attackers can exploit MySQL root privileges obtained via the injection to write arbitrary files using INTO DUMPFILE, enabling deployment of a PHP webshell to the web-accessible roundcube logs directory and achieving remote code execution as the cwpsvc account.
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 confidenceControl Web Panel before 0.9.8.1225 has a blind SQL injection in the userRes POST parameter at the user endpoint. Unauthenticated attackers can inject arbitrary SQL queries, leveraging MySQL root privileges to write files via INTO DUMPFILE, deploy a PHP webshell to the web-accessible roundcube logs directory, and achieve remote code execution as the cwpsvc account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Check Control Web Panel versionLocate the CWP version information, typically found in the admin interface under system info or in version-related configuration filesAffected if Version is earlier than 0.9.8.1225
-
Verify user endpoint exposureConfirm the /user endpoint exists and accepts POST requests with userRes parameterAffected if Endpoint is accessible without authentication and the userRes parameter is accepted
-
Check MySQL user privileges for CWPExamine the MySQL user configured for Control Web Panel, typically in CWP configuration files related to database connectionsAffected if MySQL user has root privileges or overly permissive grants
-
Inspect roundcube logs directory accessibilityLocate the roundcube logs directory and verify it is web-accessible (located within the web root or accessible via HTTP)Affected if Roundcube logs are in a web-accessible directory with write permissions
Environment is affected if CWP version is before 0.9.8.1225 and the user endpoint accepting userRes POST parameter is exposed without authentication.
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.
dbcve · scopedUpgrade Control Web Panel to version 0.9.8.1225 or later. Additionally, implement input validation on the userRes parameter, restrict MySQL user privileges from root, and remove or restrict write access to web-accessible directories like roundcube logs.
Control Web Panel version 0.9.8.1225 or later
- Backup the current Control Web Panel installation and configuration
- Update Control Web Panel to version 0.9.8.1225 or later using the official CWP update mechanism
- Verify the update was successful by checking the CWP version in the admin panel
- Confirm the userRes endpoint now properly sanitizes input
- Review MySQL privileges to ensure the cwpsvc user no longer has unnecessary root-level access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57517 — 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-57517 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