# CVE-2006-2948: Information disclosure in n/a

> Remote attackers can access the database file to steal usernames and passwords due to insufficient access control.

- **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:** 12 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-72hw-4cxx-c98r

## What is CVE-2006-2948?

CVE-2006-2948 is a medium-severity vulnerability in n/a, published on 12 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A-CART 2.0 stores the acart2_0.mdb file under the web document root with insufficient access control, which allows remote attackers to obtain username and password information.

## Which versions are affected by CVE-2006-2948?

It affects 1 product.


Products: Alan Ward A-Cart.

## How do I fix CVE-2006-2948?

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

## Is CVE-2006-2948 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6111](https://insights.sbomify.com/CVE-2006-6111/): SQL injection in n/a (high 7.5)
- [CVE-2004-1873](https://insights.sbomify.com/CVE-2004-1873/): SQL injection vulnerability in category.asp in A-CART Pro and A-CART 2.0 allows remote attackers to gain privileges via the catcode parameter. (high 7.5)
- [CVE-2004-1874](https://insights.sbomify.com/CVE-2004-1874/): Multiple cross-site scripting (XSS) vulnerabilities in (1) deliver.asp and (2) billing.asp in A-CART Pro and A-CART 2.0 allow remote attacke (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2948 and fix it if it is affected.

What it is: CVE-2006-2948 is a medium-severity vulnerability in n/a, published on 12 Jun 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2948 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-2006-2948/ (Markdown: https://insights.sbomify.com/CVE-2006-2948/index.md)
```

## Sources

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

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