# CVE-2007-6299: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in Drupal via vulnerable contributed modules, potentially compromising database integrity and confidentiality.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vqfh-h9j7-97mw

## What is CVE-2007-6299?

CVE-2007-6299 is a high-severity SQL injection vulnerability in Drupal Drupal, published on 10 Dec 2007. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in Drupal and vbDrupal 4.7.x before 4.7.9 and 5.x before 5.4 allow remote attackers to execute arbitrary SQL commands via modules that pass input to the taxonomy_select_nodes function, as demonstrated by the (1) taxonomy_menu, (2) ajaxLoader, and (3) ubrowser contributed modules.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Drupal Drupal.

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

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

## Is CVE-2007-6299 being exploited?

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

## 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-6299 and fix it if it is affected.

What it is: CVE-2007-6299 is a high-severity SQL injection vulnerability in Drupal Drupal, published on 10 Dec 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-6299 in the wild and no public exploit code.

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

## Sources

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

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