# CVE-2007-4093: Information disclosure in n/a

> Remote attackers can download the user database containing usernames and encrypted passwords by directly requesting the exposed database file.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/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:** 30 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8p79-497p-9qx5

## What is CVE-2007-4093?

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

### Official description

Minb Is Not a Blog (minb) stores sensitive information under the web root with insufficient access control, which allows remote attackers to download a database containing usernames and encrypted passwords via a direct request for db/users.db.

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

It affects 1 product.


Products: Minb Minb Is Not a Blog.

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

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

## Is CVE-2007-4093 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7005](https://insights.sbomify.com/CVE-2008-7005/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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