CVE-2005-3817
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 Softbiz Web Host Directory Script 1.1 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) cid parameter in search_result.php, (2) sbres_id parameter in review.php, (3) cid parameter in browsecats.php, (4) h_id parameter in email.php, and (5) an unspecified parameter to the search module.
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 Softbiz Web Host Directory Script 1.1 and earlier allow remote attackers to execute arbitrary SQL commands via the cid parameter in search_result.php and browsecats.php, the sbres_id parameter in review.php, the h_id parameter in email.php, and an unspecified parameter to the search module.
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.1CVSS 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 installed version of Softbiz Web Host Directory ScriptCheck the version information in the script's documentation, readme file, or the main configuration file (typically in the includes or config directory). Look for a version number or check the script's admin panel if available.Affected if The installed version is 1.1 or earlier (or if the version cannot be determined and the script appears to be the original unpatched release)
-
Locate vulnerable PHP filesSearch the web root directory for the files: search_result.php, browsecats.php, review.php, and email.php. These files should be present in the main script directory.Affected if Any of these four PHP files exist in the web-accessible directory
-
Inspect cid parameter usage in search_result.php and browsecats.phpOpen search_result.php and browsecats.php in a text editor and search for the 'cid' parameter. Check if it is used directly in SQL queries without proper escaping, parameterized queries, or input validation functions.Affected if The 'cid' parameter is directly inserted into SQL queries without sanitization (e.g., no mysql_real_escape_string, no prepared statements)
-
Inspect sbres_id parameter in review.phpOpen review.php and locate the 'sbres_id' parameter. Examine how it is used in SQL queries - look for direct concatenation into query strings.Affected if The 'sbres_id' parameter is used in SQL queries without input validation or escaping
-
Inspect h_id parameter in email.phpOpen email.php and find where 'h_id' is used. Check if it is incorporated into SQL statements without proper sanitization.Affected if The 'h_id' parameter is included in SQL queries without escaping or prepared statements
A system is affected if it runs Softbiz Web Host Directory Script version 1.1 or earlier and contains the vulnerable PHP files (search_result.php, browsecats.php, review.php, email.php) where user-supplied parameters are used directly in SQL queries without sanitization.
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 dataApply parameterized queries (prepared statements) or proper input validation and sanitization to all user-supplied parameters (cid, sbres_id, h_id) in the affected PHP files before using them in SQL queries; alternatively, upgrade to a patched version if available.
- Consultation3.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 $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3817 — 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-2005-3817 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