CVE-2006-1324
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 · uneditedCross-site scripting (XSS) vulnerability in acp/lib/class_db_mysql.php in Woltlab Burning Board (wBB) 2.3.4 allows remote attackers to inject arbitrary web script or HTML via the errormsg parameter when a SQL error is generated.
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 confidenceCross-site scripting (XSS) vulnerability in the MySQL database class (acp/lib/class_db_mysql.php) of Woltlab Burning Board 2.3.4. The errormsg parameter, which is populated when SQL errors occur, is not properly sanitized before being output in HTML context, allowing injection of arbitrary JavaScript or HTML.
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.0.2pl2e_lite<= 2.3.4CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 Woltlab Burning Board installationLocate the installation directory and check for the presence of Woltlab Burning Board files, typically in the web root or a dedicated directory.Affected if Woltlab Burning Board software is present on the server
-
Determine installed versionCheck the version file or footer of the admin control panel. Common locations include a version.php file or the ACP footer which often displays the version number.Affected if Version is 2.3.4 or lower, or 1.0.2pl2e_lite or lower
-
Locate the vulnerable fileNavigate to acp/lib/class_db_mysql.php within the installation directory.Affected if The file acp/lib/class_db_mysql.php exists in the installation
-
Inspect error message handling codeOpen class_db_mysql.php and search for code that outputs the errormsg parameter, particularly in areas handling SQL errors. Look for instances where errormsg is echoed or printed without htmlspecialchars() or equivalent encoding.Affected if The errormsg parameter is output directly to HTML without sanitization
-
Verify SQL error display functionalityTrigger a deliberate SQL error through the admin control panel or logs, then inspect the rendered HTML page source to see if user-controlled error content appears unescaped.Affected if SQL errors render with unescaped characters in the browser
The environment is affected if Woltlab Burning Board version 2.3.4 or lower (or 1.0.2pl2e_lite or lower) is installed and the errormsg parameter from SQL errors is output in HTML without proper encoding.
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 output encoding/escaping of the errormsg parameter when rendering SQL error messages in the admin control panel. Use htmlspecialchars() or equivalent context-appropriate encoding before outputting any user-controlled data.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1324 — 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-1324 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