dbcve.org
Parallels Plesk PanelApplication · Parallels

CVE-2011-4739

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 Control Panel in Parallels Plesk Panel 10.2.0 build 20110407.20 generates a password form field without disabling the autocomplete feature, which makes it easier for remote attackers to bypass authentication by leveraging an unattended workstation, as demonstrated by forms in smb/my-profile 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 confidence

The Control Panel in Parallels Plesk Panel 10.2.0 generates password form fields without the autocomplete='off' attribute, allowing browsers to cache credentials in the web interface. Attackers with physical access to an unattended workstation can retrieve stored credentials from the browser cache to bypass authentication.

MitigationAdd autocomplete='off' attribute to all password form fields in the affected Plesk Panel pages (smb/my-profile and related files), and implement session timeout policies to reduce the window of opportunity for credential theft from unattended sessions.

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_build20110407.20

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 the installed Plesk Panel version
    Log into the Plesk Panel administrative interface and navigate to Home > Updates > Check for Updates, or run the command: plesk --version. Alternatively, check the file /usr/local/psa/version if accessible.
    Affected if The installed version matches 10.2.0_build20110407.20 exactly
  2. Locate password form fields in the web interface
    Access the Plesk Panel login page and the 'My Profile' or 'smb/my-profile' section where password change forms exist. Use browser developer tools (F12) or view the page source to identify all <input type='password'> HTML elements.
    Affected if Password input fields are present in the Plesk Panel web interface
  3. Inspect autocomplete attribute on password fields
    Examine the HTML source of the login page and password change forms. Look for the autocomplete attribute on each <input type='password'> tag. Verify whether autocomplete='off' is present or missing.
    Affected if The password form fields lack the autocomplete='off' attribute (autocomplete is either present with a different value or absent entirely)

You are affected if running Parallels Plesk Panel version 10.2.0_build20110407.20 AND the password form fields in the web interface do not include autocomplete='off', allowing browsers to cache credentials.

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

Add autocomplete='off' attribute to all password form fields in the affected Plesk Panel pages (smb/my-profile and related files), and implement session timeout policies to reduce the window of opportunity for credential theft from unattended sessions.

Recommended fix Moderate confidence

Upgrade to Plesk Panel 10.4.0 or later (or latest available 10.x/11.x version)

  1. 1. Back up the current Parallels Plesk Panel configuration and all hosted websites data.
  2. 2. Obtain the latest version of Parallels Plesk Panel (version 10.4.0 or later recommended, as subsequent releases addressed this and other security issues).
  3. 3. Before upgrading, review the Plesk upgrade documentation and ensure system requirements are met.
  4. 4. Perform the upgrade in a staging environment first to verify compatibility with existing configurations and hosted sites.
  5. 5. Execute the upgrade following Parallels official upgrade procedures.
  6. 6. After upgrade, verify that password form fields in the Control Panel (particularly in smb/my-profile) now have autocomplete disabled.
  7. 7. Test authentication flows and confirm the fix is applied.
  8. 8. Deploy the upgraded version to production after successful staging validation.
Caveat Upgrading Plesk Panel may affect existing configurations, custom themes, or extensions; thorough testing in staging is recommended before production deployment

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-4739 — 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-4739 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