CVE-2005-3937
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 · uneditedSQL injection vulnerability in Softbiz B2B Trading Marketplace Script 1.1 and earler allows remote attackers to execute arbitrary SQL commands via the cid parameter in (1) selloffers.php, (2) buyoffers.php, (3) products.php, or (4) profiles.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 confidenceSQL injection vulnerability in Softbiz B2B Trading Marketplace Script allows remote attackers to execute arbitrary SQL commands via the unprotected cid parameter in selloffers.php, buyoffers.php, products.php, and profiles.php. The application fails to properly sanitize user input before using it in SQL queries.
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.
-
Locate Softbiz B2B Trading Marketplace Script installationSearch the web server document root for directories or files containing 'softbiz' or 'b2b', or look for the specific affected files: selloffers.php, buyoffers.php, products.php, and profiles.php.Affected if Any of these files exist in the web server directories.
-
Determine the installed versionOpen the script's main PHP files or any version.php, readme.txt, or install.php file to find the version number displayed or defined.Affected if The version is 1.1 or any version lower than 1.1.
-
Verify the vulnerable files existCheck for the presence of selloffers.php, buyoffers.php, products.php, and profiles.php in the installation directory.Affected if One or more of these files exist in the application.
-
Inspect the cid parameter handling in the codeOpen each affected PHP file and search for code that uses the 'cid' parameter in SQL queries without proper sanitization functions like mysql_real_escape_string, addslashes, or prepared statements.Affected if The code uses $_GET['cid'] or $_REQUEST['cid'] directly in SQL queries without input sanitization.
-
Confirm the application is accessible over the networkAttempt to access one of the affected PHP files via HTTP (e.g., http://yourserver/path/selloffers.php?cid=1) to verify the application is live and the attack surface is exposed.Affected if The application responds to HTTP requests and the vulnerable parameter is accepted.
A user is affected if the Softbiz B2B Trading Marketplace Script version 1.1 or lower is installed, the affected PHP files exist, and the cid parameter is used 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/sanitization on the cid parameter across all affected files. If the software is obsolete, consider migration to a maintained solution.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3937 — 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-3937 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