CVE-2011-4742
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 has web pages containing e-mail addresses that are not intended for correspondence about the local application deployment, which allows remote attackers to obtain potentially sensitive information by reading a page, as demonstrated by smb/user/list 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 Panel 10.2.0 control panel exposes email addresses in web pages (such as smb/user/list) that were not intended for correspondence about local application deployment, allowing remote attackers to harvest potentially sensitive administrative contact information.
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 'sw-cp-server' service, or by accessing the Plesk control panel web interface on port 8443, or by searching for Plesk-related directories in /usr/local/ or /opt/Affected if Plesk Panel is not installed on the system
-
Determine the installed Plesk Panel versionLog into the Plesk control panel as administrator and navigate to the About section, or run the command: /usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --show-versionAffected if The installed version is 10.2.0_build20110407.20
-
Confirm the web interface is accessibleAttempt to access the Plesk control panel login page at https://<server-ip>:8443/ or http://<server-ip>:8880/Affected if The web interface is not accessible (no exposure via web)
-
Check for exposed email addresses in user listAfter logging in, navigate to the SMB > Users or Users page (URL path typically contains /smb/user/list) and examine the displayed user information for email addresses that should not be visibleAffected if Email addresses are displayed in the user list interface when they were not intended for correspondence
A user is affected if Parallels Plesk Panel version 10.2.0_build20110407.20 is installed and the web interface exposes email addresses in the user list or similar pages.
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 dataUpgrade to a patched version of Plesk Panel that removes or properly handles the exposed email addresses, or configure the control panel to suppress display of non-essential contact information in the web 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-4742 — 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-4742 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