CVE-2007-3963
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 cross-site scripting (XSS) vulnerabilities in UseBB 1.0.7, and possibly other 1.0.x versions, allow remote attackers to inject arbitrary web script or HTML via the PATH_INFO (PHP_SELF) to (1) upgrade-0-2-3.php, (2) upgrade-0-3.php, or (3) upgrade-0-4.php in install/, a different vulnerability than CVE-2005-4193.
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 confidenceUseBB 1.0.7 contains multiple XSS vulnerabilities in the install/upgrade scripts (upgrade-0-2-3.php, upgrade-0-3.php, upgrade-0-4.php). The PATH_INFO variable (PHP_SELF) is not sanitized before being output in HTML, allowing remote attackers to inject arbitrary JavaScript or HTML via crafted URLs.
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= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0_rc1= 1.0_rc2= 1.0_rc3CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 UseBB installation directorySearch the web root for the UseBB installation by looking for characteristic files such as index.php, config.php, or the inc/ directory that are part of UseBB. Common paths include /forums/, /usebb/, or the web root itself.Affected if UseBB is installed on the server and the install/ directory is present.
-
Identify UseBB versionCheck the version.php file in the inc/ directory or any version file that came with the installation. Alternatively, view the footer of any UseBB page or check the version mentioned in index.php or a similar main file.Affected if The installed version is 1.0.x (including 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7) or one of the release candidates (1.0_rc1, 1.0_rc2, 1.0_rc3).
-
Verify install directory existsCheck for the presence of the install/ directory within the UseBB installation root. Look for directories named 'install' or similar.Affected if The install/ directory exists and is accessible on the web server.
-
Confirm vulnerable upgrade scripts existCheck if any of these files exist in the install/ directory: upgrade-0-2-3.php, upgrade-0-3.php, upgrade-0-4.php. List the contents of the install/ directory to verify.Affected if One or more of these specific upgrade scripts (upgrade-0-2-3.php, upgrade-0-3.php, upgrade-0-4.php) are present in the install/ directory.
You are affected if UseBB versions 1.0 through 1.0.7 or release candidates are installed, the install/ directory exists, and the vulnerable upgrade scripts (upgrade-0-2-3.php, upgrade-0-3.php, upgrade-0-4.php) are present and accessible.
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 dataSanitize the PHP_SELF variable using htmlspecialchars() or equivalent encoding before outputting it in HTML forms. Alternatively, remove or restrict access to the install/ directory in production environments.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3963 — 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-3963 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