CVE-2011-4756
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 · uneditedParallels Plesk Small Business Panel 10.2.0 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 domains/sitebuilder_edit.php 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 confidenceParallels Plesk Small Business Panel 10.2.0 fails to set the HTTPOnly flag on session cookies in Set-Cookie headers. Without this flag, cookies are accessible via JavaScript, allowing attackers to steal session identifiers through cross-site scripting (XSS) vulnerabilities.
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.
-
Verify Parallels Plesk Small Business Panel versionLocate the Plesk installation and determine the exact version number. On Linux servers, check /usr/local/psa/version or use the plesk version command. On Windows, check the registry or Plesk control panel about page.Affected if The installed version is exactly 10.2.0 (the only version listed as affected for this CVE).
-
Identify session cookies from PleskLog into the Plesk control panel and use browser developer tools (F12) or a proxy tool to capture HTTP responses. Look for Set-Cookie headers during login and authentication processes.Affected if Session cookies are present in the response headers.
-
Inspect Set-Cookie headers for HTTPOnly flagExamine each Set-Cookie header returned by Plesk authentication endpoints. Check if the HttpOnly attribute is present in the cookie definition.Affected if The Set-Cookie header does NOT contain the HttpOnly attribute (case-insensitive), meaning the cookie can be accessed via JavaScript.
-
Verify cookie accessibility via JavaScriptIf possible, access the Plesk control panel and use browser console to execute document.cookie and verify if session identifiers are exposed.Affected if Session cookie values appear in document.cookie output, confirming they are accessible to JavaScript and the HTTPOnly flag is missing.
The environment is affected if running Parallels Plesk Small Business Panel exactly version 10.2.0 and session cookies lack the HttpOnly attribute in their Set-Cookie headers, allowing XSS-based session theft.
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 dataAdd the HTTPOnly attribute to all Set-Cookie headers, particularly in domains/sitebuilder_edit.php and related authentication handlers. Upgrade to a patched version if available.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4756 — 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-4756 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