CVE-2006-7047
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 · uneditedinclude.php in Shoutpro 1.0 might allow remote attackers to bypass IP ban restrictions via a URL in the path parameter that points to an alternate bannedips.php file. NOTE: this issue was originally reported as remote file inclusion, but CVE analysis suggests that this cannot be used for code execution.
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 confidenceinclude.php in Shoutpro 1.0 contains a path traversal vulnerability where the path parameter can be manipulated to point to an alternate bannedips.php file, allowing attackers to bypass IP ban restrictions. While originally reported as remote file inclusion, analysis confirms it cannot lead to arbitrary code execution but still allows bypassing IP-based access controls.
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.0CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 Shoutpro 1.0 installationLocate the Shoutpro installation directory on the server. Look for the presence of include.php and other core Shoutpro files (such as shoutpro.php, index.php) that are characteristic of Shoutpro 1.0.Affected if Shoutpro 1.0 is installed and the include.php file exists in the web-accessible directory.
-
Identify the vulnerable include.php fileSearch for the include.php file within the Shoutpro installation. This file typically handles the inclusion of configuration files and is where the path traversal vulnerability exists.Affected if The include.php file is present and contains code that accepts a 'path' parameter for including files.
-
Verify the path parameter is accessibleTest whether the include.php script accepts a 'path' parameter via GET or POST request. Attempt to access include.php?path= to see if the parameter is processed without proper validation.Affected if The include.php file processes a 'path' parameter without validating that it points to the expected bannedips.php location.
-
Check the bannedips.php inclusion logicExamine the include.php source code to confirm it includes a bannedips.php file based on the user-controllable path parameter. Look for code patterns like 'include($path."/bannedips.php")' or similar dynamic inclusion.Affected if The code constructs the bannedips.php path using unvalidated user input from the path parameter, allowing attackers to specify an alternate location.
-
Assess IP ban bypass riskDetermine if an attacker could supply a path to a malicious or alternate bannedips.php file that lacks the legitimate IP restrictions. Attempt to include a path to a different bannedips.php location outside the intended directory.Affected if The path parameter allows traversal outside the intended directory, enabling the inclusion of a modified or alternate bannedips.php file that bypasses IP-based access controls.
A user is affected if Shoutpro 1.0 is installed with the include.php file accessible and the path parameter allows manipulation to include an alternate bannedips.php file, thereby bypassing IP ban restrictions.
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 validation of the path parameter to ensure only legitimate, whitelisted paths can be used for including the bannedips.php file, or remove the ability to specify arbitrary paths entirely.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-7047 — 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-7047 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