CVE-2005-4380
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 Bitweaver 1.1 and 1.1.1 beta allow remote attackers to execute arbitrary SQL commands via the (1) sort_mode parameter to (a) fisheye/list_galleries.php, (b) messages/message_box.php, and (c) users/my.php; the (2) post_id parameter to (d) blogs/view_post.php; and the (3) blog_id parameter to (e) blogs/view.php, which are not properly cleansed by the convert_sortmode function in kernel/BitDb.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 confidenceMultiple SQL injection vulnerabilities in Bitweaver 1.1 and 1.1.1 beta allow remote attackers to execute arbitrary SQL commands via the sort_mode parameter in fisheye/list_galleries.php, messages/message_box.php, and users/my.php; the post_id parameter in blogs/view_post.php; and the blog_id parameter in blogs/view.php, all due to insufficient input validation in the convert_sortmode function within kernel/BitDb.php.
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.1= 1.1.1_betaCVSS 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.
-
Confirm Bitweaver installationLocate the Bitweaver installation directory and identify the main version file or header that displays the version numberAffected if Bitweaver is not installed or version cannot be determined
-
Check installed version against affected rangesCompare your installed Bitweaver version to 1.1 or 1.1.1_beta as reported by the applicationAffected if The installed version is 1.1 or 1.1.1_beta
-
Verify affected PHP files existCheck for the presence of fisheye/list_galleries.php, messages/message_box.php, users/my.php, blogs/view_post.php, and blogs/view.php in the web rootAffected if Any of these files exist in the installation
-
Locate vulnerable convert_sortmode functionExamine kernel/BitDb.php for the convert_sortmode function and verify it uses unsanitized user input in SQL queriesAffected if The convert_sortmode function exists and processes sort_mode, post_id, or blog_id parameters without proper validation
-
Test parameter handling externallyIf web access is available, observe whether the sort_mode, post_id, and blog_id parameters are passed directly into SQL queries without sanitizationAffected if The application accepts and processes these parameters without parameterized queries
A user is affected if Bitweaver version 1.1 or 1.1.1_beta is installed and the vulnerable convert_sortmode function in kernel/BitDb.php processes user-supplied parameters from the listed PHP files without input validation.
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 parameterized queries in the convert_sortmode function and all affected PHP files to sanitize user-supplied parameters before using them in SQL queries.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4380 — 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-4380 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