# CVE-2000-0254: Information disclosure in n/a

> Remote attackers can access shopping cart database and configuration data by manipulating specific URL parameters in the dansie shopping cart application.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v93j-3f23-p5mq

## What is CVE-2000-0254?

CVE-2000-0254 is a medium-severity vulnerability in n/a, published on 22 Jan 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The dansie shopping cart application cart.pl allows remote attackers to obtain the shopping cart database and configuration information via a URL that references either the env, db, or vars form variables.

## Which versions are affected by CVE-2000-0254?

It affects 1 product.


Products: Craig Dansie Dansie Shopping Cart.

## How do I fix CVE-2000-0254?

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

## Is CVE-2000-0254 being exploited?

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

Public exploit code:

- Dansie Shopping Cart 3.0.4 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0253](https://insights.sbomify.com/CVE-2000-0253/): Business logic in n/a (critical 10.0)
- [CVE-2005-2217](https://insights.sbomify.com/CVE-2005-2217/): Information disclosure in n/a (medium 5.0)
- [CVE-2000-0252](https://insights.sbomify.com/CVE-2000-0252/): Command injection in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0254 and fix it if it is affected.

What it is: CVE-2000-0254 is a medium-severity vulnerability in n/a, published on 22 Jan 2001. 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-2000-0254 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-2000-0254/ (Markdown: https://insights.sbomify.com/CVE-2000-0254/index.md)
```

## Sources

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

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