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

> Remote attackers can download login credentials from a publicly accessible file, leading to potential account takeover.

- **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:** 24 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gg9q-rhfx-24wv

## What is CVE-2007-5063?

CVE-2007-5063 is a medium-severity vulnerability in n/a, published on 24 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Adam Scheinberg Flip 3.0 and earlier stores sensitive information under the web root with insufficient access control, which allows remote attackers to download a file containing login credentials via a direct request for var/users.txt.

Weakness: CWE-255

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

It affects 1 product.


Products: Adam Scheinberg Flip.

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

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

## Is CVE-2007-5063 being exploited?

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

Public exploit code:

- Flip 3.0 - Remote Password Hash Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-3311](https://insights.sbomify.com/CVE-2008-3311/): PHP remote file inclusion vulnerability in config.php in Adam Scheinberg Flip 3.0 allows remote attackers to execute arbitrary PHP code via (high 7.5)
- [CVE-2007-5062](https://insights.sbomify.com/CVE-2007-5062/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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