CVE-2007-3326
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 directory traversal vulnerabilities in vBulletin 3.x.x allow remote attackers to redirect visitors to arbitrary local files via a .. (dot dot) in (1) the loc parameter to admincp/index.php and (2) the Hyperlink information URl field for post Topic in showthread.php, enabling cross-site scripting (XSS) and other attacks, a different vulnerability than CVE-2005-3025.2.
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 confidencevBulletin 3.x.x contains directory traversal vulnerabilities in admincp/index.php (loc parameter) and showthread.php (Hyperlink information URL field). Attackers can use '..' sequences to redirect users to arbitrary local files, enabling cross-site scripting (XSS) and related attacks.
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.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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:N/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.
-
Confirm vBulletin installationLook for vBulletin characteristic files such as /includes/config.php or /admincp/index.php in the web root directory.Affected if vBulletin files are present on the server
-
Identify installed vBulletin versionCheck the version.php file typically located in the /includes directory, or log into the admin control panel and navigate to the version information page.Affected if The installed version is 3.0.0 or any 3.x.x version prior to patches
-
Verify affected file admincp/index.php existsCheck for the presence of admincp/index.php in the web root.Affected if The file admincp/index.php exists and is accessible via the web server
-
Test loc parameter for directory traversalAttempt a controlled request to admincp/index.php with a loc parameter containing a path traversal sequence such as loc=../includes/config.php (only in authorized testing environments).Affected if The loc parameter accepts and processes '..' sequences without sanitization
-
Verify showthread.php vulnerability contextCheck for the presence of showthread.php in the web root and determine if user-generated content or URL fields are processed without proper validation.Affected if showthread.php exists and processes URL fields without rejecting path traversal sequences
A user is affected if vBulletin version 3.0.0 (or other 3.x versions with the vulnerability) is installed and the admincp/index.php and showthread.php files handle the loc parameter and URL fields without filtering directory traversal sequences.
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 strict input validation on the loc parameter and URL fields to reject path traversal sequences. Upgrade to a supported vBulletin version or apply vendor patches if available.
- 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-2007-3326 — 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-2007-3326 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