# CVE-2007-3446: Hardcoded credentials in n/a

> Remote attackers can gain unauthorized access using default demo credentials in BugMall Shopping Cart.

- **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:** 27 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-96j2-crfj-6gpp

## What is CVE-2007-3446?

CVE-2007-3446 is a high-severity vulnerability in n/a, published on 27 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BugMall Shopping Cart 2.5 and earlier has a default username "demo" and password "demo," which allows remote attackers to obtain login access.

## Which versions are affected by CVE-2007-3446?

It affects 1 product.


Products: Bugmall Shopping Cart.

## How do I fix CVE-2007-3446?

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

## Is CVE-2007-3446 being exploited?

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

Public exploit code:

- bugmall shopping cart 2.5 - SQL Injection / Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3447](https://insights.sbomify.com/CVE-2007-3447/): SQL injection in n/a (medium 6.8)
- [CVE-2007-3448](https://insights.sbomify.com/CVE-2007-3448/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3446 and fix it if it is affected.

What it is: CVE-2007-3446 is a high-severity vulnerability in n/a, published on 27 Jun 2007. 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-2007-3446 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-2007-3446/ (Markdown: https://insights.sbomify.com/CVE-2007-3446/index.md)
```

## Sources

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

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