CVE-2005-0284
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 addentry.php in Woltlab Burning Book 1.0 Gold, 1.1.1e, and possibly other versions, allows remote attackers to execute arbitrary SQL commands via the user-agent parameter.
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 addentry.php allows remote attackers to execute arbitrary SQL commands via the user-agent HTTP header parameter, which is not properly sanitized before being used in a SQL query.
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_gold= 1.1.1eCVSS 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.
-
Identify Woltlab Burning Book installationSearch the web server file system for Woltlab Burning Book files, typically located in the web root directory. Look for directories containing 'burningbook' or 'wbb' in the name, and identify the main application files.Affected if The application is Woltlab Burning Book installed on the server
-
Check addentry.php file existenceLocate the addentry.php file within the Woltlab Burning Book installation directory. This file is typically found in the root or a script subdirectory of the application.Affected if The addentry.php file exists in the Woltlab Burning Book installation
-
Determine the installed versionCheck the version identifier of Woltlab Burning Book. This is typically found in a version file, changelog, or within the main index.php file. Common version markers include '1.0_gold' or '1.1.1e'.Affected if The installed version is 1.0_gold or 1.1.1e specifically
-
Verify web accessibility of addentry.phpConfirm that addentry.php is accessible via HTTP/HTTPS requests from the web. This file processes form submissions including HTTP headers. Attempt to access it through a web browser or curl request to verify it handles requests.Affected if addentry.php is accessible and processes HTTP requests including the user-agent header
-
Inspect SQL query handling in addentry.phpOpen addentry.php in a text editor and examine the code around line numbers that handle the user-agent HTTP header. Look for SQL queries that directly incorporate the user-agent value without sanitization or use of prepared statements.Affected if The code directly embeds the user-agent header value into SQL queries without using parameterized queries or input sanitization
A user is affected if they have Woltlab Burning Book version 1.0_gold or 1.1.1e installed with the addentry.php file accessible and the user-agent header being used directly 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 dataUpgrade to a patched version of Woltlab Burning Book if available; otherwise, refactor addentry.php to use parameterized queries/prepared statements instead of directly embedding the user-agent value in SQL statements.
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-0284 — 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-0284 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