CVE-2011-4746
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 billing system for Parallels Plesk Panel 10.3.1_build1013110726.09 does not disable the SSL 2.0 protocol, which makes it easier for remote attackers to conduct spoofing attacks by leveraging protocol weaknesses.
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 billing system retains SSL 2.0 protocol support, which contains known cryptographic weaknesses allowing remote attackers to perform man-in-the-middle and spoofing attacks. SSL 2.0 is obsolete and should be disabled in favor of TLS protocols.
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.3.1_build1013110726.09CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 if the Plesk Panel web interface is accessible on your server (typically port 8443) or check for Plesk installation directories and processes.Affected if Plesk Panel is not installed on the system, the CVE is not applicable.
-
Check installed Plesk Panel versionAccess the Plesk Panel admin interface and navigate to the About page, or run theplesk bin panel --version command if you have CLI access.Affected if The installed version matches exactly 10.3.1_build1013110726.09, indicating the specific affected build.
-
Inspect web server SSL/TLS protocol configurationExamine the Apache or IIS configuration files used by Plesk for the billing interface. Look for SSLProtocol or similar directives. In Apache, check ssl.conf or the Plesk Apache configuration directory.Affected if SSL 2.0 is explicitly enabled in the configuration (e.g., 'SSLProtocol all' or 'SSLProtocol +SSLv2 +SSLv3').
-
Test SSL 2.0 protocol acceptanceUse an SSL scanning tool such as nmap with the ssl-enum-ciphers script or OpenSSL s_client to attempt a connection using the -ssl2 flag to the Plesk Panel port (8443). Example: openssl s_client -connect yourserver:8443 -ssl2Affected if The server accepts SSL 2.0 connections, confirming the vulnerability is present.
Your environment is affected if Parallels Plesk Panel version 10.3.1_build1013110726.09 is installed AND the web server accepts SSL 2.0 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 dataDisable SSL 2.0 in the web server configuration (Apache/IIS) and ensure only TLS 1.0 or higher protocols are enabled for the Plesk Panel billing interface.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4746 — 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-4746 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