# CVE-2004-2732: nbmember.cgi in Netbilling 2.0 allows remote attackers to obtain sensitive information via the cmd=test option, which can be leveraged to de


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p894-4749-f3jh

## What is CVE-2004-2732?

CVE-2004-2732 is a medium-severity vulnerability in n/a, published on 9 Oct 2007. 

### Official description

nbmember.cgi in Netbilling 2.0 allows remote attackers to obtain sensitive information via the cmd=test option, which can be leveraged to determine the access key.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2004-2732?

It affects 1 product.


Products: Netbilling Netbilling.

## How do I fix CVE-2004-2732?

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

## Is CVE-2004-2732 being exploited?

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

Public exploit code:

- Netbilling NBMEMBER Script - Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2732 and fix it if it is affected.

What it is: CVE-2004-2732 is a medium-severity vulnerability in n/a, published on 9 Oct 2007. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2732 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-2004-2732/ (Markdown: https://insights.sbomify.com/CVE-2004-2732/index.md)
```

## Sources

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

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