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

> Remote attackers can inject and execute arbitrary EJBQL commands via the order parameter in JBoss Seam, potentially leading to code execution.

- **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:** Yes
- **Published:** 18 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9vxv-w3hg-m494

## What is CVE-2007-6433?

CVE-2007-6433 is a high-severity code injection vulnerability in n/a, published on 18 Dec 2007. It can be exploited over the network, with no action from the victim.

### Official description

The getRenderedEjbql method in the org.jboss.seam.framework.Query class in JBoss Seam 2.x before 2.0.0.CR3 allows remote attackers to inject and execute arbitrary EJBQL commands via the order parameter.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Jboss Seam.

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

Upgrade to a fixed version.

## Is CVE-2007-6433 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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