CVE-2006-2245
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 auction\auction_common.php in Auction mod 1.3m for phpBB allows remote attackers to execute arbitrary PHP code via a URL in the phpbb_root_path parameter.
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 confidenceRemote File Inclusion vulnerability in Auction mod 1.3m for phpBB where the auction_common.php file does not properly validate the phpbb_root_path parameter, allowing attackers to inject remote PHP URLs and execute arbitrary code.
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.0m= 1.2m= 1.3mCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 the Auction mod installationSearch for auction_common.php in your phpBB installation directory, typically in the mods folder under path such as /phpBB2/mods/auction/ or /phpBB2/includes/ or similar mod directories.Affected if The file auction_common.php exists on the server, indicating the Auction mod is installed.
-
Identify the Auction mod versionOpen auction_common.php and search for version information in comments at the top of the file, or check for a version file in the same directory (such as info_auction.php or a version constant).Affected if The version is 1.0m, 1.2m, or 1.3m, matching the affected versions.
-
Verify the auction module is enabledCheck your phpBB admin panel to confirm whether the Auction mod is listed as active/enabled in the MODs section.Affected if The Auction mod is enabled and accessible on the forum.
-
Check for the vulnerable parameter handlingInspect auction_common.php for the phpbb_root_path parameter usage. Look for code that includes or requires files using this parameter without sanitization (search for 'phpbb_root_path' in include, require, or include_once statements).Affected if The code uses phpbb_root_path in dynamic include/require statements without validating that it points to a trusted local path.
A user is affected if the phpBB Auction mod versions 1.0m, 1.2m, or 1.3m are installed and enabled, with auction_common.php present and handling phpbb_root_path without proper validation.
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 dataEither upgrade the Auction mod to a patched version or remove/disable the vulnerable auction module. If continued use is required, implement strict input validation on the phpbb_root_path parameter to only allow trusted local paths.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2245 — 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-2245 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