CVE-2011-4729
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 Server Administration Panel in Parallels Plesk Panel 10.2.0_build1011110331.18 does not include the HTTPOnly flag in a Set-Cookie header for a cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie, as demonstrated by cookies used by login_up.php3 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 Server Administration Panel in Parallels Plesk Panel 10.2.0 fails to set the HTTPOnly flag on session cookies, specifically in login_up.php3 and other authentication-related files. This allows JavaScript access to cookies via cross-site scripting (XSS) attacks, enabling attackers to steal session credentials.
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_build1011110331.18CVSS 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.
-
Determine installed Plesk Panel versionRun the command:plesk bin panel -v or check the file /usr/local/psa/versionAffected if The version displayed matches 10.2.0_build1011110331.18 exactly
-
Identify session cookies from the admin login pageAccess the Plesk admin login page at /login_up.php3 using a browser, then use browser developer tools or a tool like curl to inspect the Set-Cookie headers for PHPSESSID or similar session cookiesAffected if Session cookies are present but the HTTPOnly attribute is missing from the Set-Cookie header
-
Verify cookie header configuration in authentication scriptsExamine the source code of /login_up.php3 (typically located in /usr/local/psa/admin/htdocs/ or /var/www/html/plesk/ directory) for session_set_cookie_params or setcookie callsAffected if The code does not include the HTTPOnly flag parameter (typically the 7th parameter or 'httponly' => true in array format)
-
Test for HTTPOnly protection via JavaScriptFrom an authenticated session in the Plesk admin panel, use browser console to execute:document.cookie and verify that session-related cookies (like psa_session) are accessibleAffected if Session cookies are visible via document.cookie, indicating they lack HTTPOnly protection
You are affected if your Plesk Panel version is exactly 10.2.0_build1011110331.18 AND session cookies from the admin login page do not include the HTTPOnly flag in their Set-Cookie 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 dataUpgrade to a patched version of Parallels Plesk Panel that includes HTTPOnly flag support for cookies, or migrate to a supported Plesk version.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4729 — 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-4729 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