# CVE-2007-5416: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in Drupal by exploiting a variable unset bug via crafted callback parameters.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 12 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6x23-g67f-x44h

## What is CVE-2007-5416?

CVE-2007-5416 is a medium-severity code injection vulnerability in Drupal Drupal, published on 12 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Drupal 5.2 and earlier does not properly unset variables when the input data includes a numeric parameter with a value matching an alphanumeric parameter's hash value, which allows remote attackers to execute arbitrary PHP code by invoking the drupal_eval function through a callback parameter to the default URI, as demonstrated by the _menu[callbacks][1][callback] parameter.  NOTE: it could be argued that this vulnerability is due to a bug in the unset PHP command (CVE-2006-3017) and the proper fix should be in PHP; if so, then this should not be treated as a vulnerability in Drupal.

Weakness: CWE-189

## Which versions are affected by CVE-2007-5416?

It affects 1 product.


Products: Drupal Drupal.

## How do I fix CVE-2007-5416?

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

## Is CVE-2007-5416 being exploited?

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

Public exploit code:

- Drupal 5.2 - PHP Zend Hash ation Vector (exploitdb)

## Other vulnerabilities in Drupal Drupal

- [CVE-2026-9082](https://insights.sbomify.com/CVE-2026-9082/): Drupal Core SQL Injection (critical 9.8, exploited in the wild)
- [CVE-2020-13671](https://insights.sbomify.com/CVE-2020-13671/): Drupal core Un-restricted Upload of File (high 8.8, exploited in the wild)
- [CVE-2019-6340](https://insights.sbomify.com/CVE-2019-6340/): Drupal Core Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2009-3352](https://insights.sbomify.com/CVE-2009-3352/): Other in n/a (critical 10.0)
- [CVE-2024-55636](https://insights.sbomify.com/CVE-2024-55636/): Drupal core - Less critical - Gadget chain - SA-CORE-2024-006 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5416 and fix it if it is affected.

What it is: CVE-2007-5416 is a medium-severity code injection vulnerability in Drupal Drupal, published on 12 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-2007-5416 exists.

Affected product: Drupal Drupal. 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-2007-5416/ (Markdown: https://insights.sbomify.com/CVE-2007-5416/index.md)
```

## Sources

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

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