# CVE-2008-6199: Information disclosure in n/a

> Remote attackers can access sensitive backup data by directly requesting backup.php, exposing database contents without authentication.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/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:** 20 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pccp-7962-ch9h

## What is CVE-2008-6199?

CVE-2008-6199 is a medium-severity vulnerability in n/a, published on 20 Feb 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

2532designs 2532|Gigs 1.2.2 and earlier allows remote attackers to trigger a backup and obtain sensitive information via a direct request to backup.php, which creates backup.sql under the web root with insufficient access control.

Weakness: CWE-264

## Which versions are affected by CVE-2008-6199?

It affects 1 product.


Products: 2532gigs 2532gigs.

## How do I fix CVE-2008-6199?

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

## Is CVE-2008-6199 being exploited?

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

Public exploit code:

- 2532/Gigs 1.2.2 - Arbitrary Database Backup/Download (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-4585](https://insights.sbomify.com/CVE-2007-4585/): Path traversal in n/a (high 7.5)
- [CVE-2008-6902](https://insights.sbomify.com/CVE-2008-6902/): File upload in n/a (medium 6.8)
- [CVE-2008-6907](https://insights.sbomify.com/CVE-2008-6907/): SQL injection in n/a (medium 6.8)
- [CVE-2008-6901](https://insights.sbomify.com/CVE-2008-6901/): Path traversal in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6199 and fix it if it is affected.

What it is: CVE-2008-6199 is a medium-severity vulnerability in n/a, published on 20 Feb 2009. 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-2008-6199 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-2008-6199/ (Markdown: https://insights.sbomify.com/CVE-2008-6199/index.md)
```

## Sources

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

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