CVE-2007-1695
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 includes/usercp_register.php in phpBB 2.0.19 allows remote attackers to execute arbitrary PHP code via a URL in the phpbb_root_path parameter. NOTE: this issue has been disputed by third-party researchers, stating that the file checks for a global constant and cannot be accessed directly
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 confidenceRemote file inclusion vulnerability in phpBB 2.0.19's includes/usercp_register.php allows arbitrary PHP code execution through the phpbb_root_path parameter. The vulnerability enables attackers to inject malicious code by supplying a URL to the parameter. However, third-party researchers dispute the exploitability, claiming the file includes a global constant check preventing direct access.
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= 2.0.19CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Confirm phpBB versionLocate the version file (usually version.php in the includes directory or check the admin panel) and identify the installed version numberAffected if The installed version is exactly 2.0.19
-
Verify vulnerable file existsCheck for the presence of includes/usercp_register.php in the web rootAffected if The file exists at includes/usercp_register.php in the phpBB installation directory
-
Inspect the global constant checkOpen includes/usercp_register.php and search for a check that defines or verifies a constant (such as defined( IN_PHPBB ) or similar) near the beginning of the fileAffected if The constant check is missing, commented out, or can be bypassed, making the file directly accessible without authentication
-
Review PHP configuration settingsCheck php.ini or use phpinfo() to verify the values of allow_url_fopen and allow_url_include settingsAffected if allow_url_fopen or allow_url_include is enabled, allowing remote URL inclusion
-
Check file permissions and web server accessVerify that includes/usercp_register.php is accessible via the web server without requiring administrator authenticationAffected if The file can be accessed directly via HTTP without proper authentication checks
A user is affected if phpBB version 2.0.19 is installed, the includes/usercp_register.php file exists, and the global constant check is missing or bypassable, combined with allow_url_fopen being enabled in PHP configuration.
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 dataVerify the disputed global constant check in the affected file; if exploitable, upgrade phpBB to the latest version or apply vendor patches. Additionally, disable allow_url_fopen and allow_url_include in PHP configuration as a defense-in-depth measure.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1695 — 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-1695 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