CVE-2004-1515
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 (1) ttlast.php and (2) last10.php in vBulletin 3.0.x allows remote attackers to execute arbitrary SQL statements via the fsel parameter, as demonstrated using last.php.
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 3.0.x allows remote attackers to execute arbitrary SQL statements via the fsel parameter in ttlast.php and last10.php files.
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= 3.0.0= 3.0.0_beta_2= 3.0.0_can4= 3.0.0_rc4= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.0.6= 3.0_beta_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.
-
Identify vBulletin installation and versionLocate the vBulletin version file - typically in ./includes/version.php or check the admin control panel footer for the version number. Compare against affected versions: 3.0.0, 3.0.0_beta_2, 3.0.0_can4, 3.0.0_rc4, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.0_beta_2.Affected if Installed version matches any of the affected 3.0.x versions listed above.
-
Verify presence of vulnerable script filesCheck the web root directory for the files ttlast.php and last10.php in the forum directory (typically /forums/ or /vb/). These are calendar-related scripts.Affected if Either ttlast.php or last10.php exists in the web-accessible forum directory.
-
Confirm fsel parameter handling in vulnerable codeExamine the source code of ttlast.php and last10.php. Look for direct use of the 'fsel' parameter in SQL queries without proper sanitization or use of parameterized queries.Affected if The code shows the fsel parameter being used directly in SQL queries without escaping or prepared statements.
-
Test web access to vulnerable endpointsAttempt to access ttlast.php and last10.php via HTTP (for example: https://yourforum.com/ttlast.php?fsel=test). If the scripts respond, they are web-accessible.Affected if The vulnerable PHP files are accessible over the web and accept the fsel parameter.
A system is affected if it runs any vBulletin 3.0.x version between 3.0.0 and 3.0.6 and has the ttlast.php or last10.php files accessible via web with the fsel parameter being used unsafely in 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 dataUpgrade vBulletin to a patched version or implement proper input validation/parameterized queries for the fsel parameter.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-1515 — 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-1515 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