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

> Remote attackers can execute arbitrary PHP code via eval injection in the phpRPC library's decode function, affecting applications using this component.

- **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:** 7 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7x6m-57gq-rcf3

## What is CVE-2006-1032?

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

### Official description

Eval injection vulnerability in the decode function in rpc_decoder.php for phpRPC 0.7 and earlier, as used by runcms, exoops, and possibly other programs, allows remote attackers to execute arbitrary PHP code via the base64 tag.

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

It affects 1 product.


Products: Phprpc Phprpc.

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

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

## Is CVE-2006-1032 being exploited?

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

Public exploit code:

- phpRPC Library 0.7 - XML Data Decoding Remote Code Execution (1) (exploitdb)
- phpRPC < 0.7 - Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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