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

> Authenticated administrators can execute arbitrary PHP code via a null byte injection in the index parameter of Archangel Weblog.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h4fq-c9g5-9qmg

## What is CVE-2006-0945?

CVE-2006-0945 is a medium-severity code injection vulnerability in n/a, published on 1 Mar 2006. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

PHP remote file include vulnerability in admin/index.php in Archangel Weblog 0.90.02 allows remote authenticated administrators to execute arbitrary PHP code via a URL ending in a NULL (%00) in the index parameter.

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

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

It affects 1 product.


Products: Archangelmgt Weblog.

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

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

## Is CVE-2006-0945 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0944](https://insights.sbomify.com/CVE-2006-0944/): Auth bypass in n/a (high 7.5)
- [CVE-2007-2574](https://insights.sbomify.com/CVE-2007-2574/): Path traversal in n/a (medium 5.0)
- [CVE-2006-4091](https://insights.sbomify.com/CVE-2006-4091/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0945 is a medium-severity code injection vulnerability in n/a, published on 1 Mar 2006. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0945 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-0945/ (Markdown: https://insights.sbomify.com/CVE-2006-0945/index.md)
```

## Sources

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

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