CVE-2007-5889
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 IDMOS 1.0 Alpha (aka Phoenix) allow remote attackers to execute arbitrary PHP code via a URL in the site_absolute_path parameter to (1) admin.php, (2) menu_add.php, and (3) menu_operation.php in administrator/, different vectors than CVE-2007-5294.
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 confidenceIDMOS 1.0 Alpha contains multiple PHP remote file inclusion vulnerabilities where the site_absolute_path parameter in admin.php, menu_add.php, and menu_operation.php under the administrator/ directory is used in unsafe include/require statements without input validation. This allows remote attackers to supply a malicious URL that gets processed as PHP code, enabling arbitrary code execution on the server.
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.0-alphaCVSS 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 IDMOS 1.0-alpha installationSearch for the presence of the administrator/ directory and its PHP files: admin.php, menu_add.php, menu_operation.phpAffected if Any of these files exist in the web root or a subdirectory
-
Verify allow_url_include is enabledCheck php.ini for the directive 'allow_url_include = On' or run 'php -i' or 'phpinfo()' to inspect this settingAffected if allow_url_include is set to On (1) in PHP configuration
-
Inspect admin.php for unsafe include patternOpen administrator/admin.php and search for include/require statements using the site_absolute_path variable without validation, such as include($site_absolute_path . '/path')Affected if The code contains include() or require() statements that directly use the site_absolute_path parameter without input sanitization
-
Inspect menu_add.php for unsafe include patternOpen administrator/menu_add.php and examine include/require statements that incorporate the site_absolute_path parameterAffected if The file uses site_absolute_path in include/require calls without whitelist validation
-
Inspect menu_operation.php for unsafe include patternOpen administrator/menu_operation.php and look for include/require statements that use the site_absolute_path variableAffected if The file contains unsafe include/require using site_absolute_path without validation
A user is affected if IDMOS 1.0-alpha is installed, the vulnerable PHP files exist, and PHP's allow_url_include is enabled, allowing remote attackers to inject malicious URLs via the site_absolute_path parameter.
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 PHP's allow_url_include setting, implement strict input validation on the site_absolute_path parameter using whitelist validation, and migrate to modern secure software as this legacy application is likely unsupported.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5889 — 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-5889 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