CVE-2007-3066
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 · uneditedMultiple PHP remote file inclusion vulnerabilities in php(Reactor) 1.2.7 and earlier allow remote attackers to execute arbitrary PHP code via a URL in the pathtohomedir parameter to (1) view.inc.php, (2) users.inc.php, (3) updatecms.inc.php, and (4) polls.inc.php in inc/; and other unspecified files, different vectors than CVE-2006-3983.
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 (RFI) vulnerabilities in php(Reactor) 1.2.7 and earlier allow attackers to inject arbitrary PHP code through the pathtohomedir parameter in multiple inc/ files (view.inc.php, users.inc.php, updatecms.inc.php, polls.inc.php). The vulnerable include() calls permit remote code execution by specifying a URL instead of a local path.
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.2.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate php(Reactor) installationSearch for php(Reactor) directories or files on the web server. Common locations include the web root directory. Look for directories named 'php(Reactor)', 'phpreactor', or similar. Also search for the vulnerable inc/ files: view.inc.php, users.inc.php, updatecms.inc.php, polls.inc.php.Affected if php(Reactor) is found in the web root or any accessible directory.
-
Determine php(Reactor) versionCheck for a version file, readme, or any file containing version information within the php(Reactor) installation directory. Common files include version.php, readme.txt, or the main index.php which may display version info.Affected if The installed version is 1.2.7 or any version lower than 1.2.7.
-
Inspect vulnerable include() statementsOpen each of these files from the inc/ directory: view.inc.php, users.inc.php, updatecms.inc.php, and polls.inc.php. Search for include() or require() calls that use the 'pathtohomedir' parameter without proper validation.Affected if The code contains include() or require() statements using the pathtohomedir parameter without sanitization (no check to reject URLs or ../ paths).
-
Check PHP allow_url_include settingCreate a PHP script with '<?php echo ini_get("allow_url_include"); ?>' and access it through the web server, or check php.ini directly for the allow_url_include directive.Affected if allow_url_include is set to On or 1 - this makes the RFI vulnerability exploitable for remote code execution.
A user is affected if php(Reactor) version 1.2.7 or earlier is installed, the vulnerable inc/ files exist with the insecure pathtohomedir include() calls, and allow_url_include is 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 dataDisable allow_url_include in PHP configuration, implement strict input validation on the pathtohomedir parameter to reject URLs, and apply vendor patches or upgrade to a secure version.
- 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-2007-3066 — 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-3066 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