# CVE-2006-7047: Security feature bypass in n/a

> Remote attackers can bypass IP ban restrictions in Shoutpro by manipulating the path parameter to reference an alternate file.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m99j-42qj-56rq

## What is CVE-2006-7047?

CVE-2006-7047 is a medium-severity vulnerability in n/a, published on 24 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

include.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.

Weakness: CWE-264

## Which versions are affected by CVE-2006-7047?

It affects 1 product.


Products: Shoutpro Shoutpro.

## How do I fix CVE-2006-7047?

No fix has been published for CVE-2006-7047 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-7047 being exploited?

There is no known exploitation of CVE-2006-7047 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-2141](https://insights.sbomify.com/CVE-2007-2141/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7047 and fix it if it is affected.

What it is: CVE-2006-7047 is a medium-severity vulnerability in n/a, published on 24 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-7047 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-7047/ (Markdown: https://insights.sbomify.com/CVE-2006-7047/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-7047
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-7047
- OSV: https://osv.dev/vulnerability/CVE-2006-7047

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-7047/
Summaries are generated and may contain mistakes; the official description above is the record.