CVE-2011-4758
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 · uneditedParallels Plesk Small Business Panel 10.2.0 receives cleartext password input over HTTP, which allows remote attackers to obtain sensitive information by sniffing the network, as demonstrated by forms in smb/auth and certain other files.
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 confidenceParallels Plesk Small Business Panel 10.2.0 transmits password credentials in cleartext over unencrypted HTTP connections. Attackers on the same network or anywhere along the traffic path can sniff and intercept these credentials. The vulnerability exists in authentication forms within smb/auth and related files.
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.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
- 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.
-
Identify installed Plesk versionUse the Plesk version command or check the control panel interface for the exact version number. On Linux, you can often find this in /usr/local/psa/version or via the 'plesk version' CLI command.Affected if The installed version is exactly 10.2.0 (no other versions are affected per the provided information)
-
Verify HTTP is enabled for the control panelCheck if the Plesk web server is listening on unencrypted HTTP port 80. You can use commands like 'netstat -tlnp' or 'ss -tlnp' to see which ports the web server is bound to.Affected if Port 80 is open and accepting connections for the Plesk panel interface
-
Confirm authentication endpoints accept HTTPAttempt to access the smb/auth login page over HTTP (http://your-server/smb/auth or similar path). Verify the page loads without redirecting to HTTPS.Affected if The authentication form loads over HTTP without automatic redirection to HTTPS
-
Inspect login form submission methodView the HTML source of the login form at smb/auth and check if the form action URL uses http:// rather than https://, or if the page lacks any transport security indicators.Affected if The form action submits to an HTTP URL or no secure transport is enforced
A user is affected if they have Plesk Small Business Panel version 10.2.0 installed AND the authentication interface is accessible over unencrypted HTTP connections.
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 dataEnable HTTPS/SSL for all authentication endpoints and the entire control panel. Obtain and install a valid SSL certificate, configure the web server to enforce SSL/TLS, and redirect all HTTP traffic to HTTPS.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4758 — 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-4758 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