dbcve.org
Parallels Plesk PanelApplication · Parallels

CVE-2011-4732

HIGH · 10.0 CVSS v2.0 Published 2011-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Server Administration Panel in Parallels Plesk Panel 10.2.0_build1011110331.18 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 account/power-mode-logout 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 confidence

The Server Administration Panel in Parallels Plesk Panel 10.2.0 omits the Content-Type header's charset parameter for certain resources, which could allow remote attackers to exploit an interpretation conflict (likely MIME sniffing or character encoding ambiguity) involving files like account/power-mode-logout and other unspecified endpoints.

MitigationUpgrade from Plesk Panel 10.2.0 to a patched version that properly includes charset parameters in Content-Type headers, or implement explicit Content-Type headers with charset on affected admin panel resources.

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
Parallels Plesk PanelApplication
Affected:= 10.2.0_build1011110331.18

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Plesk Panel version
    Access the Plesk login page or check the product version through the admin interface. Typically found in Help > About or the main login page footer which displays the build number.
    Affected if The version shown is exactly 10.2.0_build1011110331.18 or falls within the 10.2.0 build series.
  2. Confirm Server Administration Panel is accessible
    Attempt to reach the admin panel login page (typically https://your-server:8443/ or http://your-server:8880/). Verify the page loads successfully.
    Affected if The admin panel is reachable and running on the affected version.
  3. Inspect Content-Type header on affected endpoint
    Use a browser developer tool or command-line tool (curl -I) to request the /account/power-mode-logout endpoint. Examine the Content-Type header in the response.
    Affected if The Content-Type header is present but missing the charset parameter (e.g., shows "text/html" instead of "text/html; charset=utf-8").

A user is affected if they are running Plesk Panel version 10.2.0_build1011110331.18 and the admin panel endpoint returns Content-Type headers without charset parameters, creating potential MIME sniffing ambiguity.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade from Plesk Panel 10.2.0 to a patched version that properly includes charset parameters in Content-Type headers, or implement explicit Content-Type headers with charset on affected admin panel resources.

Recommended fix Moderate confidence

Plesk Onyx 17.x or later (modern supported release)

  1. 1. Back up the current Plesk configuration and all hosted websites data.
  2. 2. Review the Plesk upgrade documentation for migrating from version 10.x to a supported version.
  3. 3. Ensure the operating system meets the requirements for the target Plesk version.
  4. 4. Perform a test upgrade in a non-production environment first.
  5. 5. Schedule a maintenance window for the production upgrade.
  6. 6. Execute the upgrade following Plesk documentation, or consider a fresh install of current Plesk (Onyx 17.x or later) and migrate configurations.
Caveat Upgrading from Plesk Panel 10.x to modern Plesk may require migration steps, could break legacy configurations, and may require OS version upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Parallels Plesk Panel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-4732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-4732 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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