CVE-2006-5029
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 thread.php in WoltLab Burning Board (wBB) 2.3.x allows remote attackers to obtain the version numbers of PHP, MySQL, and wBB via the page parameter. NOTE: this issue might be a forced SQL error. Also, the original report was disputed by a third party for 2.3.3 and 2.3.4.
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 · moderate confidenceSQL injection vulnerability in thread.php of WoltLab Burning Board 2.3.x allows remote attackers to inject malicious SQL via the page parameter, potentially revealing PHP, MySQL, and wBB version numbers. The issue may be a forced SQL error rather than traditional injection, and version applicability is disputed for 2.3.3 and 2.3.4.
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= 2.3.0= 2.3.1= 2.3.2= 2.3.3= 2.3.4= 2.3.5CVSS 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.
-
Verify WoltLab Burning Board installationLocate the installation directory and check for wbb2 version files, typically in the root or a 'wbb2' folder. Look for version.php or check the footer of pages for version information.Affected if The software is installed and the version cannot be confirmed as patched (versions 2.3.0-2.3.5 are listed as affected).
-
Confirm installed version numberAccess the admin control panel or look for version indicator files in the installation. Compare the found version against the affected range: 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.3.5.Affected if The installed version is 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, or 2.3.5.
-
Locate thread.php fileCheck for the presence of thread.php in the web root or forum directory. This file is required for the vulnerability to be exploitable.Affected if thread.php exists in the accessible web directory.
-
Test page parameter for SQL error behaviorSend a crafted request to thread.php with an abnormal page parameter value (e.g., thread.php?page=99999999 or thread.php?page=invalid) and observe if SQL errors or version information is returned in the response.Affected if The page parameter accepts unsanitized input and triggers SQL errors or reveals version information in error messages.
The environment is affected if WoltLab Burning Board version 2.3.0 through 2.3.5 is installed, thread.php is accessible, and the page parameter allows arbitrary input that produces SQL errors or version disclosure.
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 dataUpgrade to a patched version of wBB or apply input validation/sanitization to the page parameter in thread.php to prevent SQL injection attempts.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5029 — 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-5029 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