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

> Remote attackers can execute arbitrary SQL commands via login parameters in E-Commerce Scripts, potentially compromising database integrity and confidentiality.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 1 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-36gf-p6rh-cj9x

## What is CVE-2007-4121?

CVE-2007-4121 is a critical SQL injection vulnerability in n/a, published on 1 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in admin.aspx in E-Commerce Scripts Shopping Cart Script, Multi-Vendor E-Shop Script, and Auction Script allow remote attackers to execute arbitrary SQL commands via the (1) EmailAdd (Username) and (2) Pass (password) parameters.  NOTE: some of these details are obtained from third party information.

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

It affects 3 products.


Products: E-Commerce Solutions Auction Script, E-Commerce Solutions Multi-Vendor E-Shop Script, E-Commerce Solutions Shopping Cart Script.

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

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

## Is CVE-2007-4121 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4121 is a critical SQL injection vulnerability in n/a, published on 1 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4121 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-4121/ (Markdown: https://insights.sbomify.com/CVE-2007-4121/index.md)
```

## Sources

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

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