CVE-2011-4767
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 Site Editor (aka SiteBuilder) feature in Parallels Plesk Small Business Panel 10.2.0 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 js/Wizard/Status.js 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 confidenceThe Site Editor (SiteBuilder) feature in Parallels Plesk Small Business Panel 10.2.0 exposes email addresses in publicly accessible web JavaScript files (such as js/Wizard/Status.js) that were not intended for external correspondence. This information disclosure vulnerability allows remote attackers to harvest these email addresses through direct page access.
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.
-
Confirm Plesk Small Business Panel versionCheck the installed version of Parallels Plesk Small Business Panel. This is typically visible in the admin interface or can be retrieved via the Plesk command line utility: 'plesk --version' or through the admin panel's system information page.Affected if The installed version is Parallels Plesk Small Business Panel 10.2.0 exactly.
-
Verify SiteBuilder feature is installedCheck if the SiteBuilder (Site Editor) module is installed on the panel. This can be verified by reviewing the available modules in the Plesk admin interface or by checking for SiteBuilder-related directories in the web root.Affected if SiteBuilder is installed and enabled on the panel.
-
Locate the vulnerable JavaScript fileAccess the file path js/Wizard/Status.js within the SiteBuilder web directory. The typical location would be under the SiteBuilder web root, for example: /usr/local/psa/admin/htdocs/domains/datapacks/xml/sitebuilder/js/Wizard/Status.js or similar paths under the web document root.Affected if The file js/Wizard/Status.js exists in the SiteBuilder web-accessible directory.
-
Inspect for exposed email addressesOpen the Status.js file and search for email address patterns (strings containing '@' and domain extensions). Review the content for any email addresses that were not intended for public disclosure.Affected if The file contains one or more email addresses that are visible in the publicly accessible JavaScript file.
A user is affected if they are running exactly version 10.2.0 of Parallels Plesk Small Business Panel with the SiteBuilder feature installed, and the JavaScript files in SiteBuilder's web directory contain exposed email addresses.
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 or obfuscate the unintended email addresses from SiteBuilder JavaScript files, or disable the SiteBuilder feature if not required. Audit other SiteBuilder files for similar exposure.
- Consultation2.0 h
- Implementation3.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 $2,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4767 — 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-4767 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