# CVE-2003-0557: SQL injection in n/a

> Remote attackers can extract sensitive user information via SQL injection in the login password field of StoreFront.

- **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:** 15 Jul 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-76hh-5qhw-7w85

## What is CVE-2003-0557?

CVE-2003-0557 is a high-severity SQL injection vulnerability in n/a, published on 15 Jul 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in login.asp for StoreFront 6.0, and possibly earlier versions, allows remote attackers to obtain sensitive user information via SQL statements in the password field.

## Which versions are affected by CVE-2003-0557?

It affects 1 product.


Products: Lagarde Storefront.

## How do I fix CVE-2003-0557?

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

## Is CVE-2003-0557 being exploited?

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

Public exploit code:

- LaGarde StoreFront 5.0 Shopping Cart - 'login.asp' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-1341](https://insights.sbomify.com/CVE-2008-1341/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0557 and fix it if it is affected.

What it is: CVE-2003-0557 is a high-severity SQL injection vulnerability in n/a, published on 15 Jul 2003. 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-2003-0557 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-2003-0557/ (Markdown: https://insights.sbomify.com/CVE-2003-0557/index.md)
```

## Sources

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

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