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

> Remote attackers can execute arbitrary PHP code in Ay System Solutions CMS via remote file inclusion in specific parameters.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-53pp-49v8-q8r5

## What is CVE-2006-4441?

CVE-2006-4441 is a high-severity code injection vulnerability in n/a, published on 29 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple PHP remote file inclusion vulnerabilities in Ay System Solutions CMS 2.6 and earlier allow remote attackers to execute arbitrary PHP code via a URL in the path[ShowProcessHandle] parameter to (1) home.php or (2) impressum.php.  NOTE: the provenance of this information is unknown; the details are obtained from third party information.

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

It affects 1 product.


Products: Ay System Solutions Ay System Solutions Cms.

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

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

## Is CVE-2006-4441 being exploited?

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

Public exploit code:

- Ay System CMS 2.6 - 'main.php' Remote File Inclusion (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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