CVE-2006-3348
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 HSPcomplete 3.2.2 and 3.3 Beta and earlier allow remote attackers to execute arbitrary SQL commands via the (1) type parameter in report.php and (2) level parameter in custom_buttons.php.
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 confidenceHSPcomplete versions 3.2.2 and 3.3 Beta contain SQL injection vulnerabilities in two PHP files. The 'type' parameter in report.php and the 'level' parameter in custom_buttons.php are not properly sanitized before being used in database queries, allowing remote attackers to inject arbitrary SQL commands.
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<= 3.3_beta= 3.2.2CVSS 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 Hspcomplete installation versionLocate the HSPcomplete installation directory (typically within the web server's document root or a dedicated hosting control panel directory). Look for version identification files, such as version.php, or check the application's admin interface for the version number.Affected if The installed version matches 3.2.2 or is 3.3_beta or lower.
-
Verify report.php existsIn the HSPcomplete installation directory, locate the file named report.php. This file typically resides in admin or reporting subdirectories.Affected if The file report.php exists in the installation.
-
Inspect 'type' parameter handling in report.phpOpen report.php and search for database query code that uses the 'type' parameter. Verify whether the parameter is directly concatenated into SQL queries without sanitization or use of prepared statements.Affected if The 'type' parameter is used in SQL queries without parameterized binding or input sanitization.
-
Verify custom_buttons.php existsIn the HSPcomplete installation directory, locate the file named custom_buttons.php. This file may be found in admin, configuration, or customization subdirectories.Affected if The file custom_buttons.php exists in the installation.
-
Inspect 'level' parameter handling in custom_buttons.phpOpen custom_buttons.php and search for database query code that uses the 'level' parameter. Verify whether the parameter is directly concatenated into SQL queries without sanitization or use of prepared statements.Affected if The 'level' parameter is used in SQL queries without parameterized binding or input sanitization.
The environment is affected if HSPcomplete version 3.2.2 or 3.3_beta (or lower) is installed AND either report.php or custom_buttons.php exists with unsanitized 'type' or 'level' parameters in SQL queries.
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 parameterized queries (prepared statements) for all database queries in report.php and custom_buttons.php, and add input validation to sanitize the 'type' and 'level' parameters before use in SQL statements.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-3348 — 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-3348 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