CVE-2011-4753
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 Parallels Plesk Small Business Panel 10.2.0 allow remote attackers to execute arbitrary SQL commands via crafted input to a PHP script, as demonstrated 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 confidenceMultiple SQL injection vulnerabilities in Parallels Plesk Small Business Panel 10.2.0 allow remote unauthenticated attackers to execute arbitrary SQL commands via crafted input to PHP scripts, specifically demonstrated in domains/sitebuilder_edit.php and other files.
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
- 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.
-
Verify Parallels Plesk Small Business Panel is installedCheck for the presence of Plesk Small Business Panel installation directories, typically under /usr/local/psa or /opt/psa, or look for the Plesk control panel service running on ports 8443 or 8880Affected if The product is not installed or this is a different product
-
Confirm the exact version is 10.2.0Check the Plesk version via the admin interface, command line (plesk --version or mmm --version), or by inspecting version files in the installation directoryAffected if The installed version is not exactly 10.2.0 (the vulnerability only affects this specific version)
-
Locate the vulnerable PHP script domains/sitebuilder_edit.phpSearch for the file sitebuilder_edit.php within the Plesk web directories, typically under the /domains/ or /admin/ subdirectories of the Plesk document rootAffected if The file does not exist (may have been removed or this is a different installation variant)
-
Verify the PHP scripts are accessible via HTTP/HTTPSAttempt to access the identified vulnerable PHP scripts (such as domains/sitebuilder_edit.php) through the web server to confirm they respond to requestsAffected if The PHP scripts are not accessible or not exposed via the web server (no attack surface)
The environment is affected only if Parallels Plesk Small Business Panel version 10.2.0 is installed with the vulnerable PHP scripts (specifically domains/sitebuilder_edit.php and similar files) accessible via the web server.
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 dataRemediate by implementing parameterized queries or prepared statements in all affected PHP files, conducting a full code audit to identify additional vulnerable endpoints, and applying input validation and sanitization across the application.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4753 — 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-4753 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