CVE-2006-2675
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 · uneditedPHP remote file inclusion vulnerability in ubbt.inc.php in UBBThreads 5.x and 6.x allows remote attackers to execute arbitrary PHP code via a URL in the (1) thispath or (2) configdir parameters.
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 confidenceUBBThreads 5.x and 6.x contains a remote file inclusion vulnerability in ubbt.inc.php where the thispath and configdir parameters are not properly sanitized before being used in include/require statements. An attacker can supply a malicious URL to these parameters, causing arbitrary PHP code execution on the target server.
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<= 6.5.3= 3.4= 3.5= 5.0= 5.5.1= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.1= 6.1.1= 6.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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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.
-
Locate UBBThreads installationSearch for ubbt.inc.php or common UBBThreads directories such as /forum/, /ubbthreads/, or /boards/. Check for the presence of the main UBBThreads script files (common filenames include ubbt.inc.php, ubbthreads.php, or similar).Affected if The file ubbt.inc.php exists in the web root or a subdirectory.
-
Identify UBBThreads versionOpen the file common.php or a version file within the UBBThreads installation directory. Look for a variable such as $ubbt_version, $VERSION, or check a version.inc.php file. The affected versions range from 3.4 through 6.5.3.Affected if The installed version is 6.5.3 or lower, or matches 3.4, 3.5, 5.0, 5.5.1, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.1, 6.1.1, or 6.2.
-
Verify vulnerable script existsConfirm the file ubbt.inc.php exists in the installation. This is the file containing the vulnerable include/require statements that use the thispath and configdir parameters without sanitization.Affected if The file ubbt.inc.php is present and accessible via the web server.
-
Check PHP allow_url_include settingCreate a PHP script containing <?php echo ini_get('allow_url_include'); ?> and access it through the web server, or check the php.ini file directly.Affected if allow_url_include is set to 1 or On, which permits remote file inclusion attacks to succeed.
A user is affected if UBBThreads version 6.5.3 or lower (specifically 3.4, 3.5, 5.0, 5.5.1, 6.0-6.0.3, 6.1-6.2) is installed with ubbt.inc.php present and PHP's allow_url_include is enabled.
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 dataDisable PHP's allow_url_include setting to prevent remote file inclusion attacks. Ideally, upgrade or migrate away from UBBThreads as it is legacy software no longer under active development.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2675 — 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-2006-2675 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