# CVE-2005-1363: Multiple SQL injection vulnerabilities in MetaCart 2.0 for PayFlow allow remote attackers to execute arbitrary commands via (1) intCatalogID


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7mj8-93vr-77jg

## What is CVE-2005-1363?

CVE-2005-1363 is a high-severity vulnerability in n/a, published on 28 Apr 2005. 

### Official description

Multiple SQL injection vulnerabilities in MetaCart 2.0 for PayFlow allow remote attackers to execute arbitrary commands via (1) intCatalogID, (2) strSubCatalogID, or (3) strSubCatalog_NAME parameter to productsByCategory.asp, (4) curCatalogID, (5) strSubCatalog_NAME, (6) intCatalogID, or (7) page parameter to productsByCategory.asp or (8) intProdID parameter to product.asp.

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

It affects 1 product.


Products: Metalinks Metacart2.

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

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

## Is CVE-2005-1363 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1362](https://insights.sbomify.com/CVE-2005-1362/): Multiple SQL injection vulnerabilities in MetaCart 2.0 for Paypal allow remote attackers to execute arbitrary SQL commands via the (1) intPr (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1363 is a high-severity vulnerability in n/a, published on 28 Apr 2005. 
Exploitation: There is no known exploitation of CVE-2005-1363 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-1363/ (Markdown: https://insights.sbomify.com/CVE-2005-1363/index.md)
```

## Sources

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

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