CVE-2006-5508
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 addentry.php in WoltLab Burning Book 1.1.2 allow remote attackers to execute arbitrary SQL commands via (1) the n parameter and (2) the User-Agent HTTP header.
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 vulnerabilities exist in addentry.php of WoltLab Burning Book 1.1.2 where the 'n' parameter and User-Agent HTTP header are not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
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.2CVSS 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 WoltLab Burning Book installationSearch web server document root for WoltLab Burning Book files, typically in a directory named 'burningbook' or similar. Look for characteristic PHP files like 'index.php', 'addentry.php', or template files (*.tpl).Affected if The application is not found in the environment, then not affected.
-
Verify the exact version numberOpen the main index.php or look for a version file (often named 'version.php', 'info.php', or within an 'about' file). Search for a version string that reads exactly '1.1.2'.Affected if The installed version is exactly 1.1.2, then vulnerable.
-
Confirm addentry.php existsIn the identified WoltLab Burning Book directory, verify that addentry.php is present in the web-accessible path.Affected if addentry.php does not exist, then the specific SQL injection vector is not present.
-
Identify if 'n' parameter is processedExamine addentry.php source code or monitor HTTP requests to determine if the 'n' parameter is accepted and used in database queries without parameterized preparation.Affected if The 'n' parameter is directly concatenated into SQL queries, then exploitable.
-
Identify if User-Agent header is loggedExamine addentry.php source code or web server logs configuration to determine if the User-Agent HTTP header is captured and used in SQL queries without sanitization.Affected if User-Agent header is directly inserted into SQL queries, then exploitable.
A user is affected if WoltLab Burning Book version 1.1.2 is installed with the addentry.php file present and the application processes the 'n' parameter or User-Agent header in unparameterized SQL queries.
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 dataReplace dynamic SQL query construction with parameterized queries/prepared statements, and implement proper input validation and escaping for both the 'n' parameter and User-Agent header.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5508 — 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-5508 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