dbcve.org
PhpcoinApplication

CVE-2007-0861

HIGH · 7.5 CVSS v2.0 Published 2007-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
PHP remote file inclusion vulnerability in modules/mail/index.php in phpCOIN RC-1 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the _CCFG['_PKG_PATH_MDLS'] parameter. NOTE: this issue has been disputed by a reliable third party, who states that a fatal error occurs before the relevant code is reached

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 confidence

Remote file inclusion vulnerability in phpCOIN RC-1 and earlier allows arbitrary PHP code execution through the _CCFG['_PKG_PATH_MDLS'] parameter in modules/mail/index.php. The parameter is used in an include/require statement without validation, enabling attackers to include malicious remote PHP files. Note: This issue has been disputed by a third party claiming a fatal error occurs before the vulnerable code executes.

MitigationImplement strict input validation on the _CCFG['_PKG_PATH_MDLS'] parameter to ensure only whitelisted, local paths are accepted, or hardcode the expected path values. Additionally, ensure the configuration variable is properly initialized before use to prevent the disputed fatal error condition.

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
PhpcoinApplication
Affected:<= rc1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate phpCOIN installation
    Search the web server document root for phpCOIN files, typically in directories named /coin, /phpcoin, or at the root level. Look for index.php or config.php files containing 'phpCOIN' or '_CCFG' strings.
    Affected if phpCOIN is installed on the server in any location
  2. Identify phpCOIN version
    Check the version identifier in the source code - look for version strings in main index.php, about.php, or a version/include file. Common version markers include 'RC-1', 'rc1', or version constants.
    Affected if The installed version is RC-1 or any version number lower than RC-1 (e.g., beta, alpha releases)
  3. Verify vulnerable file exists
    Check if the file modules/mail/index.php exists within the phpCOIN installation directory. This file contains the include/require statement using the _CCFG['_PKG_PATH_MDLS'] parameter.
    Affected if The file modules/mail/index.php exists in the phpCOIN installation
  4. Inspect parameter handling in mail module
    Examine the source code of modules/mail/index.php for include or require statements that use _CCFG['_PKG_PATH_MDLS'] without sanitization. The vulnerable code would look something like include($_CCFG['_PKG_PATH_MDLS'].'...').
    Affected if The code directly uses _CCFG['_PKG_PATH_MDLS'] in an include/require without validation or filtering of the parameter value
  5. Check if parameter is externally controllable
    Test whether the _CCFG['_PKG_PATH_MDLS'] parameter can be overridden via GET or POST request to modules/mail/index.php. Attempt a controlled test including a local file to verify if the parameter is used without initialization checks.
    Affected if The parameter can be controlled via URL parameters and is not initialized/defaulted before use, allowing arbitrary file inclusion

A system is affected if phpCOIN RC-1 or earlier is installed, the modules/mail/index.php file exists, and the _CCFG['_PKG_PATH_MDLS'] parameter is used in an include statement without validation and can be controlled by an attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the _CCFG['_PKG_PATH_MDLS'] parameter to ensure only whitelisted, local paths are accepted, or hardcode the expected path values. Additionally, ensure the configuration variable is properly initialized before use to prevent the disputed fatal error condition.

Fix this in Phpcoin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0861 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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