dbcve.org
Ultimate Php BoardApplication

CVE-2006-3207

MEDIUM · 5.0 CVSS v2.0 Published 2006-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Directory traversal vulnerability in newpost.php in Ultimate PHP Board (UPB) 1.9.6 and earlier allows remote attackers to overwrite arbitrary files via a .. (dot dot) sequence and trailing null (%00) byte in the id parameter, as demonstrated by injecting a Perl CGI script using "[NR]" sequences in the message parameter, then calling close.php with modified id and t_id parameters to chmod the script. NOTE: this issue might be resultant from dynamic variable evaluation.

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 confidence

Directory traversal vulnerability in newpost.php allows remote attackers to overwrite arbitrary files via .. sequences and null byte (%00) injection in the id parameter. Attackers can inject Perl CGI scripts through message parameters and execute them via close.php by modifying id and t_id parameters to chmod the injected script executable, achieving remote code execution.

MitigationUpgrade to a patched version of UPB beyond 1.9.6 or implement strict input validation on the id parameter to reject path traversal sequences (..) and null bytes (%00), along with disabling dynamic variable evaluation in PHP.

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
Ultimate Php BoardApplication
Affected:= 1.8= 1.8.2= 1.9= 1.9.6

CVSS 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
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm UPB installation and version
    Search the web root for files containing 'Ultimate Php Board' or 'UPB' and check version.php or similar version files for version numbers matching 1.8, 1.8.2, 1.9, or 1.9.6
    Affected if UPB version is 1.8, 1.8.2, 1.9, or 1.9.6
  2. Locate vulnerable script newpost.php
    Search the application directory for newpost.php - this is the primary attack entry point
    Affected if newpost.php exists in the application web directory
  3. Locate vulnerable script close.php
    Search the application directory for close.php - this is used to execute injected scripts via t_id parameter manipulation
    Affected if close.php exists and is accessible via the web
  4. Test id parameter for path traversal
    If newpost.php is accessible, inspect the PHP code for the id parameter handling - look for lack of sanitization filtering for '..' sequences and null byte %00 in the id variable used in file operations
    Affected if The id parameter is used in file operations without filtering ../ or %00 sequences
  5. Verify CGI script injection vector
    Examine the message parameter handling in newpost.php to see if user-supplied message content can be written to disk as a file with .cgi or .pl extension
    Affected if User message content is written to disk without sanitization of file extension or content
  6. Confirm chmod capability via close.php
    Review close.php code to see if the t_id parameter can be manipulated to change file permissions on injected scripts
    Affected if close.php allows modifying file permissions on arbitrary paths via t_id parameter

A user is affected if they run any version of Ultimate Php Board between 1.8 and 1.9.6 inclusive, and the newpost.php and close.php files are accessible and process the id/t_id parameters without proper input validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of UPB beyond 1.9.6 or implement strict input validation on the id parameter to reject path traversal sequences (..) and null bytes (%00), along with disabling dynamic variable evaluation in PHP.

Fix this in Ultimate Php Board Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-3207 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-3207 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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