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

> Remote attackers can include and execute arbitrary PHP code in an unspecified FXB application via main.php.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 5 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qqf8-5vgc-xp54

## What is CVE-2006-1623?

CVE-2006-1623 is a medium-severity code injection vulnerability in n/a, published on 5 Apr 2006. It can be exploited over the network.

### Official description

Unspecified vulnerability in main.php in an unspecified "file created by Andries Bruinsma," possibly a FleXiBle Development (FXB) application, allows remote attackers to include and execute arbitrary PHP code.  NOTE: this disclosure is extremely vague and has very little information about the specific vulnerability type.  In addition, there is little public information on the named product. Finally, an XSS vector is implied in the subject line, but because there is no other information and evidence of a cut-and-paste error, it will not be assigned a separate CVE identifier unless additional information is provided.

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

It affects 1 product.


Products: Andries Bruinsma Flexible Development.

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

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

## Is CVE-2006-1623 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1623 is a medium-severity code injection vulnerability in n/a, published on 5 Apr 2006. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-1623 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-1623/ (Markdown: https://insights.sbomify.com/CVE-2006-1623/index.md)
```

## Sources

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

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