CVE-2011-4734
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 · uneditedMultiple SQL injection vulnerabilities in the Control Panel in Parallels Plesk Panel 10.2.0 build 20110407.20 allow remote attackers to execute arbitrary SQL commands via crafted input to a PHP script, as demonstrated by file-manager/ 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 confidenceMultiple SQL injection vulnerabilities exist in Parallels Plesk Panel 10.2.0 (build 20110407.20) control panel. Remote attackers can execute arbitrary SQL commands by submitting crafted input to PHP scripts, specifically including file-manager/ and other files. The vulnerability stems from insufficient input validation allowing malicious SQL payloads to be passed to the database.
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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Identify Parallels Plesk Panel versionAccess the Plesk admin interface and navigate to the About section, or check the version file at /usr/local/psa/version if you have shell access. The exact build number is displayed in the version string.Affected if The installed version shows exactly 10.2.0_build20110407.20
-
Confirm file-manager module accessibilityCheck if the file-manager PHP interface is exposed on the server. This is typically accessible at /file-manager/ or similar paths under the Plesk control panel URL.Affected if The file-manager interface is accessible without additional authentication restrictions beyond standard Plesk login
-
Review web server access logsExamine HTTP access logs for the Plesk control panel directory, looking for POST or GET requests to PHP scripts containing unusual SQL syntax, apostrophes, or UNION/SELECT keywords.Affected if Log entries show SQL-like payloads in request parameters to PHP scripts in the Plesk web directories
-
Check for unauthorized database modificationsReview database user permissions and recent database changes, particularly in the Plesk database (usually psa database) for unexpected tables or modified records.Affected if Database contains unauthorized changes or unexpected tables created after the Plesk Panel was exposed to untrusted networks
You are affected if your Parallels Plesk Panel installation is exactly version 10.2.0_build20110407.20 and the control panel is network-accessible to untrusted users.
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 addresses these SQL injection vulnerabilities. As an interim measure, restrict network access to the control panel interface (e.g., via IP whitelisting or VPN) to reduce attack surface.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4734 — 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-4734 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