CVE-2007-5035
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 html/modules/extranet_profile/main.php in openEngine 1.9 beta1 allows remote attackers to execute arbitrary PHP code via a URL in the this_module_path parameter. NOTE: this issue is disputed by CVE because PHP encounters a fatal function-call error on a direct request for the file, before reaching the include statement
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 openEngine 1.9 beta1's html/modules/extranet_profile/main.php allows arbitrary PHP code execution via the this_module_path parameter. However, the CVE includes a disputed note indicating PHP encounters a fatal function-call error before reaching the include statement on direct requests, potentially limiting exploitability.
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.9_beta1= 1.9_beta2= 1.9_beta3CVSS 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.
-
Confirm openEngine installation and versionLocate the openEngine installation directory and identify the installed version number (typically found in a version file, README, or installation manifest)Affected if The installed version is 1.9_beta1, 1.9_beta2, or 1.9_beta3
-
Verify vulnerable file existsCheck if the file html/modules/extranet_profile/main.php exists within the openEngine web root directoryAffected if The file html/modules/extranet_profile/main.php is present on the server
-
Check if extranet_profile module is enabledExamine the openEngine module configuration or directory structure to determine whether the extranet_profile module is actively enabled or loadedAffected if The extrenet_profile module is enabled and accessible via the web application
-
Inspect the vulnerable code locationOpen html/modules/extranet_profile/main.php and search for usage of the 'this_module_path' parameter in an include or require statementAffected if The code contains an include or require statement using the 'this_module_path' parameter without proper validation
You are affected if openEngine version 1.9_beta1, 1.9_beta2, or 1.9_beta3 is installed, the vulnerable file exists, and the extranet_profile module is enabled with the this_module_path parameter used in an include statement.
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 this_module_path parameter using a whitelist approach, and disable allow_url_include in PHP configuration to prevent remote file inclusions.
- 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-5035 — 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-5035 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