CVE-2007-4935
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 phpFFL 1.24 allow remote attackers to execute arbitrary PHP code via a URL in the PHPFFL_FILE_ROOT parameter to (1) admin.php, (2) custom_pages.php, (3) draft.php, (4) faq.php, (5) leagues.php, (6) livedraft.php, (7) login.php, (8) my_team.php, (9) profile.php, (10) signup.php, (11) statistics.php, (12) transactions.php, (13) program_files/admin/custom_pages.php, or (14) program_files/common.php. NOTE: the program_files/livedraft/admin.php and program_files/livedraft/livedraft.php vectors are covered by CVE-2007-4934.
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 confidenceMultiple Remote File Inclusion (RFI) vulnerabilities in phpFFL 1.24 allow remote attackers to execute arbitrary PHP code by supplying a malicious URL in the PHPFFL_FILE_ROOT parameter, which is unsafely used in include/require statements across 14 PHP 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.24CVSS 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.
-
Confirm phpFFL installation and versionSearch for phpFFL files on the server (typically in web root). Check version.php or any version indicator file for '1.24'Affected if phpFFL version 1.24 is installed
-
Locate PHP files using PHPFFL_FILE_ROOTSearch PHP source files for 'PHPFFL_FILE_ROOT' string, particularly in include() or require() statementsAffected if Files contain 'include($PHPFFL_FILE_ROOT' or 'require($PHPFFL_FILE_ROOT' patterns
-
Verify parameter is user-controllableCheck if PHPFFL_FILE_ROOT is obtained from $_GET, $_POST, or $_REQUEST without sanitization. Examine the code flow from parameter receipt to inclusionAffected if The parameter is used directly in include/require without validation or hardcoded paths
-
Test parameter injection pointSend a request with PHPFFL_FILE_ROOT pointing to an external URL (e.g., http://evil.com/shell.txt?) and check if the application attempts to include itAffected if The application includes files from arbitrary URLs provided in the parameter
-
Check PHP allow_url_include settingInspect php.ini for 'allow_url_include = On' which is required for RFI to succeed from remote URLsAffected if allow_url_include is enabled and the vulnerable code path is reachable
You are affected if phpFFL 1.24 is running and the PHPFFL_FILE_ROOT parameter reaches unsafe include/require statements without validation, especially with allow_url_include enabled.
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 dataReplace dynamic file inclusion with hardcoded paths or implement strict allowlist validation for the PHPFFL_FILE_ROOT parameter; ideally upgrade to a patched version of phpFFL.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4935 — 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-4935 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