PhpbbApplication · Phpbb Group

CVE-2006-5435

HIGH · 7.5 CVSS v2.0 Published 2006-10-20
Fix available
A fix is available. Upgrade to after 2.0.10 or later.
See remediation →
84/100
Remediation priority · High
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
PHP remote file inclusion vulnerability in groupcp.php in phpBB 2.0.10 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the phpbb_root_path parameter. NOTE: CVE and the vendor dispute this vulnerability because $phpbb_root_path is defined before use

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 · moderate confidence

Remote file inclusion vulnerability in phpBB 2.0.10 and earlier allows execution of arbitrary PHP code via the phpbb_root_path parameter in groupcp.php. The vendor disputes this finding, claiming $phpbb_root_path is defined before use, which may limit actual exploitability despite the high CVSS score.

MitigationUpgrade to a supported version of phpBB, or at minimum verify the $phpbb_root_path variable is properly initialized before inclusion operations in groupcp.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
PhpbbApplication
Affected:<= 2.0.10

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
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 checks

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

  1. Locate phpBB installation
    Search for phpBB files on the web server, typically in common web directories. Look for files like viewforum.php, viewtopic.php, or a folder named 'phpBB' or 'forum'. Check for the presence of a 'includes/constants.php' or 'config.php' file that indicates a phpBB installation.
    Affected if phpBB is installed on the server in a web-accessible directory
  2. Determine phpBB version
    Open the file 'includes/constants.php' in the phpBB installation directory and look for a line defining PHPBB_VERSION or similar version constant. Alternatively, check the 'changelog.txt' or 'docs' folder for version information. Compare the found version number to the affected range: 2.0.10 or earlier.
    Affected if The installed version is phpBB 2.0.10 or any earlier version (e.g., 2.0.9, 2.0.8, etc.)
  3. Verify groupcp.php exists and is accessible
    Check for the presence of the file 'groupcp.php' in the root phpBB directory. Confirm it is accessible via HTTP (e.g., https://example.com/forum/groupcp.php).
    Affected if groupcp.php exists and is web-accessible
  4. Inspect phpbb_root_path initialization in groupcp.php
    Open groupcp.php in a text editor and search for the variable '$phpbb_root_path'. Examine whether this variable is assigned a safe default value (such as './') BEFORE any include or require statements that use it. Look for code patterns like 'define("PHPBB_ROOT_PATH", "./");' or '$phpbb_root_path = "./";' appearing before the first include/require that references this variable.
    Affected if The variable $phpbb_root_path is NOT defined with a safe default before being used in include/require statements, allowing external control of the path parameter

A user is affected if they have phpBB version 2.0.10 or earlier installed, with groupcp.php accessible and where $phpbb_root_path is not properly initialized before use in inclusion operations.

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
Upgrade available Upgrade to a release after 2.0.10
Interim mitigation

Upgrade to a supported version of phpBB, or at minimum verify the $phpbb_root_path variable is properly initialized before inclusion operations in groupcp.php.

Fix this in Phpbb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-5435 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-5435 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