CVE-2011-4737
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 · uneditedThe Control Panel in Parallels Plesk Panel 10.2.0 build 20110407.20 includes a submitted password within an HTTP response body, which allows remote attackers to obtain sensitive information by sniffing the network, as demonstrated by password handling in client@2/domain@1/odbc/dsn@1/properties/.
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 confidenceThe Parallels Plesk Panel 10.2.0 Control Panel includes submitted passwords within HTTP response bodies, allowing remote attackers to capture sensitive credentials via network sniffing. The vulnerability exists in the ODBC DSN properties functionality where user input is echoed back in the response.
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= 10.2.0_build20110407.20CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Verify Parallels Plesk Panel installationCheck for Plesk Panel by looking for the httpd administration interface typically on ports 8443 or 8880, or check for Plesk installation directories such as /usr/local/psa or C:\Program Files\Parallels on the server filesystemAffected if The system is running Parallels Plesk Panel
-
Determine installed Plesk Panel versionAccess the Plesk administrator login page and check the version information typically displayed in the footer, or run the command 'plesk --version' or check /usr/local/psa/version on Linux systemsAffected if The version is 10.2.0 with build 20110407.20
-
Locate ODBC DSN configuration interfaceLog into the Plesk control panel as an administrator and navigate to the ODBC DSN properties section, typically found under Databases or ODBC Data Sources in the control panel navigationAffected if The ODBC DSN properties functionality is accessible and exposed via the web interface
-
Capture HTTP response from ODBC DSN form submissionUse a web proxy or browser developer tools to intercept the HTTP response when submitting or viewing ODBC DSN configuration with a password field. Inspect the response body for plaintext password dataAffected if The HTTP response body contains the submitted password in plaintext or as an echoed parameter value
The system is affected if it runs Parallels Plesk Panel version 10.2.0 build 20110407.20 with the ODBC DSN feature accessible and passwords appearing in HTTP responses.
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 dataRemove password parameters from HTTP responses by processing credentials server-side only without echoing them back. Update to a patched version of Plesk Panel if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4737 — 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-2011-4737 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