CVE-2007-2411
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 index.php in Sphider 1.2.x allows remote attackers to execute arbitrary PHP code via a URL in the include_dir parameter. NOTE: a third party disputes this vulnerability, stating that "the application is not vulnerable to this issue.
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 confidencePHP remote file inclusion vulnerability in Sphider 1.2.x index.php allows remote attackers to execute arbitrary PHP code via a URL in the include_dir parameter. This is a classic RFI vulnerability where user-supplied input is used in an include() or require() statement without proper validation, enabling attackers to include malicious remote files.
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 Sphider installationSearch for index.php files that are part of Sphider. Common paths include /search/index.php, /sphider/index.php, or at the web root. Verify the file contains Sphider branding or references to Sphider in the code comments or HTML.Affected if Sphider index.php is found on the server at any path
-
Identify Sphider versionOpen the installed index.php file and search for a version string. Look for patterns like '$version =', 'version', or '1.2' in comments or configuration variables near the top of the file.Affected if The discovered version is 1.2.7 or earlier
-
Check for vulnerable include_dir parameter handlingIn index.php, search for usage of the 'include_dir' or 'include_dir' variable in include(), require(), or similar functions. Look for code that directly passes $_GET['include_dir'] or $_REQUEST['include_dir'] to include/require statements without validation.Affected if The code directly uses the include_dir parameter from user input in include/require statements without validation
-
Verify PHP allow_url_include settingCheck the PHP configuration file (php.ini) or create a PHP info page to verify the value of 'allow_url_include'. Run 'php -i' from command line or check loaded configuration files.Affected if allow_url_include is set to On (Enabled)
A user is affected if Sphider version 1.2.7 or earlier is installed, the vulnerable include_dir parameter handling exists in index.php, and PHP allow_url_include is enabled, allowing remote file inclusion attacks.
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 dataImplement strict input validation on the include_dir parameter using a whitelist approach, or disable allow_url_include in PHP configuration. Alternatively, refactor the code to use local includes with hardcoded paths instead of user-supplied values.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2411 — 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-2411 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