# CVE-2005-4572: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via admin.php parameters, potentially compromising the shopping cart database.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xfc4-9c23-wc6x

## What is CVE-2005-4572?

CVE-2005-4572 is a high-severity SQL injection vulnerability in n/a, published on 29 Dec 2005. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in myEZshop Shopping Cart allow remote attackers to execute arbitrary SQL commands via the (1) GroupsId and (2) ItemsId parameters in admin.php.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

## Which versions are affected by CVE-2005-4572?

It affects 1 product.


Products: Myezshop Myezshop Shopping Cart.

## How do I fix CVE-2005-4572?

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

## Is CVE-2005-4572 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4571](https://insights.sbomify.com/CVE-2005-4571/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4572 and fix it if it is affected.

What it is: CVE-2005-4572 is a high-severity SQL injection vulnerability in n/a, published on 29 Dec 2005. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4572 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-2005-4572/ (Markdown: https://insights.sbomify.com/CVE-2005-4572/index.md)
```

## Sources

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

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