CVE-2004-0036
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 calendar.php for vBulletin Forum 2.3.x before 2.3.4 allows remote attackers to steal sensitive information via the eventid 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 vBulletin Forum's calendar.php file affecting versions 2.3.x before 2.3.4. Attackers can exploit the unsanitized eventid parameter to inject arbitrary SQL queries and extract sensitive information from the database.
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.0CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 the vBulletin calendar.php fileSearch your web server's document root for the calendar.php file. Common paths include /calendar.php or within a /forum/ or /vb/ directory.Affected if The calendar.php file exists and is accessible on the web server.
-
Identify the installed vBulletin versionCheck the version.php file in your vBulletin installation directory, or look for a version identifier in the admin control panel under 'System Details' or 'Version Information'.Affected if The installed version is 2.3.0 or any 2.3.x version prior to 2.3.4.
-
Confirm the calendar module is enabledLog into the vBulletin admin control panel and navigate to 'vBulletin Options' or 'Plugin System'. Verify that the calendar functionality is not disabled or set to 'no'. Alternatively, attempt to access calendar.php directly via HTTP to confirm it responds.Affected if The calendar.php file is accessible and the calendar feature is enabled in the vBulletin configuration.
-
Check for evidence of exploitation attemptsReview web server access logs for requests to calendar.php containing unusual SQL syntax in the eventid parameter, such as quotes, UNION SELECT, or other SQL keywords. Example pattern: GET /calendar.php?eventid=1' OR '1'='1Affected if Suspicious SQL injection patterns are found in logs targeting the eventid parameter.
You are affected if vBulletin calendar.php is accessible and the installed version is 2.3.0 through any 2.3.x version prior to 2.3.4.
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 vBulletin 2.3.4 or later to obtain the vendor patch. If upgrading is not immediately feasible, temporarily disable the calendar functionality or deploy WAF rules to block SQL injection attempts targeting the eventid parameter.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0036 — 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-2004-0036 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