# CVE-2006-7148: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via a file inclusion vulnerability in the usage stats script of this forum software.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hfgg-5j8v-8j94

## What is CVE-2006-7148?

CVE-2006-7148 is a critical code injection vulnerability in n/a, published on 7 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP remote file inclusion vulnerability in includes/bb_usage_stats.php in maluinfo 206.2.38 for Brazilian PHPBB allows remote attackers to execute arbitrary PHP code via the phpbb_root_path parameter.  NOTE: this might be the same issues as CVE-2006-4893.

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

It affects 1 product.


Products: Phpbb Maluinfo.

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

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

## Is CVE-2006-7148 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7148 exists.

Public exploit code:

- maluinfo 206.2.38 - 'bb_usage_stats.php' Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-7148 is a critical code injection vulnerability in n/a, published on 7 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7148 exists.

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-7148/ (Markdown: https://insights.sbomify.com/CVE-2006-7148/index.md)
```

## Sources

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

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