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

> Remote attackers can execute arbitrary PHP code via URL injection in the installed_config_file parameter of Phpjobscheduler.

- **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:** 16 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-92x7-95xv-wj4g

## What is CVE-2006-5928?

CVE-2006-5928 is a high-severity code injection vulnerability in n/a, published on 16 Nov 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 Phpjobscheduler 3.0 allow remote attackers to execute arbitrary PHP code via a URL in the installed_config_file parameter to (1) add-modify.php, (2) delete.php, (3) modify.php, and (4) phpjobscheduler.php.

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

It affects 1 product.


Products: Phpjobscheduler Phpjobscheduler.

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

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

## Is CVE-2006-5928 being exploited?

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

Public exploit code:

- Phpjobscheduler 3.0 - 'installed_config_file' File Inclusion (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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