CVE-2006-5264
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 · uneditedCross-site scripting (XSS) vulnerability in sql.php in MysqlDumper 1.21 b6 allows remote attackers to inject arbitrary web script or HTML via the db parameter.
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 confidenceCross-site scripting (XSS) vulnerability in sql.php in MysqlDumper 1.21 b6 allows remote attackers to inject arbitrary web script or HTML via the db parameter. The application fails to properly sanitize or encode user-supplied input before reflecting it in the page output.
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= 1.21CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Locate MysqlDumper installationSearch for MysqlDumper directories or files on the server (common paths include /mysqldumper, /mysql-dumper, or check web root directories). Identify the installed version by locating a version file or checking the main index.php for version information.Affected if MysqlDumper version 1.21 is found installed on the server
-
Verify sql.php existsCheck if the file sql.php exists within the MysqlDumper installation directory. Common path structure would be: [install_dir]/sql.phpAffected if sql.php file is present in the MysqlDumper installation
-
Inspect sql.php for db parameter handlingExamine the source code of sql.php and locate where the 'db' parameter is processed. Look for code that retrieves the db parameter (e.g., $_GET['db'] or $_POST['db']) and outputs it back to the page without HTML encoding (without using htmlspecialchars, htmlentities, or equivalent encoding functions).Affected if The db parameter value is output to the page without HTML entity encoding (e.g., no htmlspecialchars() wrapping when echoing the value)
-
Confirm parameter is user-controllableVerify that the db parameter can be controlled via HTTP GET or POST requests to sql.php. Check if the parameter flows from user input directly to output without sanitization.Affected if The db parameter can be set via URL or form submission and is reflected in the page output without encoding
A user is affected if MysqlDumper version 1.21 is installed, sql.php is present and accessible, and the db parameter in sql.php reflects unsanitized user input in the page output.
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 dataImplement proper input validation and output encoding for the db parameter in sql.php. At minimum, apply HTML entity encoding to all untrusted input before output.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5264 — 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-2006-5264 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