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

> Remote attackers can execute arbitrary code via eval injection in the action parameter of cart.php and page.php.

- **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:** 9 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j3w8-wjw3-m7v2

## What is CVE-2007-0134?

CVE-2007-0134 is a high-severity code injection vulnerability in n/a, published on 9 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple eval injection vulnerabilities in iGeneric iG Shop 1.0 allow remote attackers to execute arbitrary code via the action parameter, which is supplied to an eval function call in (1) cart.php and (2) page.php.  NOTE: a later report and CVE analysis indicate that the vulnerability is present in 1.4.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Igeneric Ig Shop.

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

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

## Is CVE-2007-0134 being exploited?

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

Public exploit code:

- ig shop 1.0 - Code Execution / SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2717](https://insights.sbomify.com/CVE-2007-2717/): SQL injection in n/a (high 7.5)
- [CVE-2007-0132](https://insights.sbomify.com/CVE-2007-0132/): SQL injection in n/a (high 7.5)
- [CVE-2007-0133](https://insights.sbomify.com/CVE-2007-0133/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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