CVE-2006-6415
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 admin/lib-maintenance.inc.php in phpAdsNew 2.0.4-pr2 allows remote attackers to execute arbitrary PHP code via a URL in the phpAds_path parameter, a different component than CVE-2006-3984. NOTE: this issue is disputed by CVE, since phpAds_path is used as a constant
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 phpAdsNew 2.0.4-pr2 admin/lib-maintenance.inc.php allows arbitrary PHP code execution via the phpAds_path parameter. Note: CVE disputes this issue as phpAds_path is reportedly used as a constant.
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= 2_dev_2001-10-09CVSS 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 phpAdsNew installationLocate phpAdsNew web application files on the server. Search for typical installation paths such as /var/www/html/, /home/*/public_html/, or check for directories containing phpadsnew or adserver-related files.Affected if phpAdsNew is installed on the server
-
Identify phpAdsNew versionCheck for version files, such as version.php, or examine the admin interface for version information. Look for version strings indicating 2.0.4-pr2 or 2_dev_2001-10-09.Affected if The installed version is phpAdsNew 2.0.4-pr2 or 2_dev_2001-10-09
-
Locate the affected scriptFind the file admin/lib-maintenance.inc.php within the phpAdsNew installation directory. Verify the file exists and examine its contents.Affected if The file admin/lib-maintenance.inc.php exists in the phpAdsNew installation
-
Examine phpAds_path parameter handlingReview the code in lib-maintenance.inc.php to determine how the phpAds_path parameter is processed. Check if it is defined as a constant (defined()) or if it accepts user-supplied input directly.Affected if phpAds_path is not defined as a constant and accepts direct user input from the request
-
Check PHP allow_url_include settingReview the PHP configuration file (php.ini) or run phpinfo() to check the allow_url_include setting.Affected if allow_url_include is enabled (On) and the phpAds_path parameter accepts remote URLs
You are affected if phpAdsNew 2.0.4-pr2 is installed, the admin/lib-maintenance.inc.php file exists, and phpAds_path is handled as a user-controllable variable rather than a defined constant, combined with allow_url_include being enabled in PHP.
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 dataSanitize or remove user control of the phpAds_path parameter, disable PHP's allow_url_include setting, or upgrade to a patched version if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6415 — 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-2006-6415 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