# CVE-2005-1032: cart.php in LiteCommerce might allow remote attackers to obtain sensitive information via invalid (1) category_id or (2) product_id parameters.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Apr 2005
- **Updated:** 10 Jul 2017

## What is CVE-2005-1032?

CVE-2005-1032 is a vulnerability, published on 9 Apr 2005. 

### Official description

cart.php in LiteCommerce might allow remote attackers to obtain sensitive information via invalid (1) category_id or (2) product_id parameters.  NOTE: this issue was originally claimed to be due to SQL injection, but the original researcher is known to be frequently inaccurate with respect to bug type and severity.  The vendor has disputed this issue, saying "These reports are credited to malicious person we refused to hire. We have not taken legal action against him only because he is located in India.  The vulnerabilites reported can not be reproduced, hence information you provide is contrary to fact." Further investigation by CVE personnel shows that an invalid SQL syntax error could be generated, but it only reveals portions of underlying database structure, which is already available in documentation from the vendor, and it does not appear to lead to path disclosure.  Therefore, this issue is not a vulnerability or an exposure, and it probably should be REJECTED

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


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

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

## Is CVE-2005-1032 being exploited?

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

Public exploit code:

- litecommerce 2004 - 'category_id' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1032 is a vulnerability, published on 9 Apr 2005. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1032 exists.

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-1032/ (Markdown: https://insights.sbomify.com/CVE-2005-1032/index.md)
```

## Sources

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

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