CVE-2011-4741
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 Control Panel in Parallels Plesk Panel 10.2.0 build 20110407.20 includes a database connection string within a web page, which allows remote attackers to obtain potentially sensitive information by reading this page, as demonstrated by client@2/domain@1/hosting/aspdotnet/.
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 Parallels Plesk Panel 10.2.0 Control Panel exposes database connection strings within a web page (specifically the /hosting/aspdotnet/ endpoint), allowing remote unauthenticated attackers to obtain potentially sensitive database credentials via direct web access.
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_build20110407.20CVSS 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.
-
Confirm Plesk Panel versionAccess the Plesk Panel administrative interface and navigate to Server > License Management or Help > About to view the installed version and build numberAffected if Version is 10.2.0 with build20110407.20
-
Test /hosting/aspdotnet/ endpoint accessibilitySend an HTTP GET request to the URL pattern: http://<plesk_server_hostname>/hosting/aspdotnet/ - no authentication should be required to access this endpointAffected if The endpoint returns an HTTP 200 OK status rather than redirecting to a login page, returning 403, or 404
-
Inspect response for credential exposureExamine the full HTTP response body from the /hosting/aspdotnet/ endpoint. Search for plaintext patterns including 'Data Source', 'Server=', 'Database=', 'User ID=', 'Password=', connection strings using semicolon-separated key=value pairs, or any visible database server hostnames and usernamesAffected if The HTML response contains any database connection strings, connection parameters with values, or credentials in plaintext
The environment is affected if running Plesk Panel version 10.2.0 build20110407.20 AND the /hosting/aspdotnet/ endpoint is accessible without authentication AND returns database connection strings in the response body.
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 dataRestrict access to the affected Control Panel pages and ensure database connection strings are not rendered in HTML output; apply vendor patches and audit similar endpoints for credential exposure.
- 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-4741 — 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-4741 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