# CVE-2004-2692: Command injection in n/a

> Remote attackers can execute arbitrary commands via backtick operators in PHP when safe mode is disabled, bypassing security restrictions.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-4h82-3wj3-6799

## What is CVE-2004-2692?

CVE-2004-2692 is a critical command injection vulnerability in n/a, published on 6 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The exec_dir PHP patch (php-exec-dir) 4.3.2 through 4.3.7 with safe mode disabled allows remote attackers to bypass restrictions and execute arbitrary commands via a backtick operator, which is not handled using the php_escape_shell_cmd function.

Weakness: CWE-264, CWE-16

## Which versions are affected by CVE-2004-2692?

It affects 1 product.


Products: Kyberdigi Labs Php-Exec-Dir.

## How do I fix CVE-2004-2692?

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

## Is CVE-2004-2692 being exploited?

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

Public exploit code:

- PHP 4.3.7 - 'php-exec-dir' Patch Command Access Restriction Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2692 and fix it if it is affected.

What it is: CVE-2004-2692 is a critical command injection vulnerability in n/a, published on 6 Oct 2007. 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-2004-2692 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-2004-2692/ (Markdown: https://insights.sbomify.com/CVE-2004-2692/index.md)
```

## Sources

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

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