CVE-2006-3797
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 DeluxeBB 1.07 and earlier allows remote attackers to bypass authentication, spoof users, and modify settings via the (1) memberpw and (2) membercookie cookies.
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 DeluxeBB 1.07 and earlier allows remote attackers to bypass authentication via specially crafted SQL in the memberpw and membercookie cookies, enabling user spoofing and modification of application settings.
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.05= 1.06= 1.07CVSS 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 DeluxeBB installationSearch the web root directory for DeluxeBB files (index.php, upload.php, or templates). Check HTTP response headers or page footers for 'DeluxeBB' branding.Affected if DeluxeBB software is found running on the server
-
Identify installed versionOpen the main index.php file, a README file, or check the database configuration file for a version string. Compare the version number to 1.05, 1.06, or 1.07.Affected if Installed version is 1.05, 1.06, or 1.07 (or any version 1.07 or earlier)
-
Verify authentication uses vulnerable cookiesLocate the authentication logic (commonly in inc/functions.php or a members.php file). Search for usage of $_COOKIE['memberpw'] or $_COOKIE['membercookie'] in SQL query contexts without sanitization.Affected if The code uses memberpw or membercookie cookie values directly in SQL queries without input validation
-
Test for SQL injection vulnerabilitySend an HTTP request with a crafted cookie value containing SQL syntax (e.g., membercookie=1' OR '1'='1) and observe if authentication behavior changes unexpectedly or if the application returns a database error.Affected if Authentication can be bypassed or unexpected results occur with SQL characters in the cookie values
The environment is affected if DeluxeBB versions 1.05 through 1.07 are running and the memberpw or membercookie cookies are 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 dataSanitize and validate cookie values (memberpw and membercookie) before using them in SQL queries, or upgrade to a patched version of DeluxeBB that properly handles authentication cookies.
- 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-2006-3797 — 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-3797 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