CVE-2011-4768
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 omits the Content-Type header's charset parameter for certain resources, which might allow remote attackers to have an unspecified impact by leveraging an interpretation conflict involving Wizard/Edit/Modules/Image and certain other files. NOTE: it is possible that only clients, not the Plesk product, could be affected by this issue.
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 · moderate confidenceThe Site Editor (SiteBuilder) feature in Parallels Plesk Small Business Panel 10.2.0 fails to include the charset parameter in Content-Type headers for certain resources, potentially causing MIME type interpretation conflicts between browsers when handling files like Wizard/Edit/Modules/Image and other unspecified 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 Parallels Plesk Small Business Panel installationCheck for the presence of Parallels Plesk Small Business Panel on the system. Common locations include /usr/local/psa or check installed packages using system package manager.Affected if The product is not installed or is a different version than 10.2.0
-
Confirm exact version 10.2.0Query the installed Plesk version using the command 'plesk --version' or check /usr/local/psa/version file.Affected if The installed version is not exactly 10.2.0
-
Verify Site Editor (SiteBuilder) feature is enabledCheck Plesk admin panel settings or configuration files for SiteBuilder module status. Look in Plesk control panel under the Site Editor settings for the affected domain.Affected if Site Editor is not accessible or not enabled for any domain
-
Inspect Content-Type headers from Site Editor resourcesUse a browser developer tool or curl to request resources under the Site Editor path such as /Wizard/Edit/Modules/Image or similar SiteBuilder URLs, and examine the Content-Type response header.Affected if Content-Type header lacks charset parameter (e.g., shows 'text/html' instead of 'text/html; charset=utf-8')
The environment is affected only if Parallels Plesk Small Business Panel version 10.2.0 is installed, the Site Editor feature is enabled, and HTTP responses from Site Editor resources omit the charset parameter in Content-Type headers.
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 dataConfigure the Site Editor to explicitly specify charset in Content-Type headers for all served resources, or disable the affected Site Editor functionality if a patch is unavailable.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4768 — 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-4768 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