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

> Remote attackers can execute arbitrary PHP code via URL injection in BASE if register_globals is enabled.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:P/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:** 31 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h78c-2562-6c4v

## What is CVE-2006-2685?

CVE-2006-2685 is a medium-severity code injection vulnerability in n/a, published on 31 May 2006. 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 Basic Analysis and Security Engine (BASE) 1.2.4 and earlier, with register_globals enabled, allows remote attackers to execute arbitrary PHP code via a URL in the BASE_path parameter to (1) base_qry_common.php, (2) base_stat_common.php, and (3) includes/base_include.inc.php.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Kevin Johnson Basic Analysis and Security Engine.

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

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

## Is CVE-2006-2685 being exploited?

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

Public exploit code:

- BASE 1.2.4 - melissa Snort Frontend Remote File Inclusion (exploitdb)
- BASE 1.2.4 - 'base_qry_common.php' Remote File Inclusion (Metasploit) (exploitdb)
- BASE base_qry_common Remote File Include (metasploit)
- BASE - 'base_qry_common' Remote File Inclusion (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-1590](https://insights.sbomify.com/CVE-2006-1590/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2685 is a medium-severity code injection vulnerability in n/a, published on 31 May 2006. 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-2685 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-2685/ (Markdown: https://insights.sbomify.com/CVE-2006-2685/index.md)
```

## Sources

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

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