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

> Authenticated users can view their own password in the HTML source of the profile page, exposing credentials to anyone with access to the page source.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3cqm-fjg8-pwww

## What is CVE-2007-6399?

CVE-2007-6399 is a medium-severity vulnerability in n/a, published on 17 Dec 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

index.php in Flat PHP Board 1.2 and earlier allows remote authenticated users to obtain the password for the current user account by reading the password parameter value in the HTML source for the page generated by a profile action.

Weakness: CWE-255

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

It affects 1 product.


Products: Myupb Flat Php Board.

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

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

## Is CVE-2007-6399 being exploited?

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

Public exploit code:

- Flat PHP Board 1.2 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6399 is a medium-severity vulnerability in n/a, published on 17 Dec 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6399 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-6399/ (Markdown: https://insights.sbomify.com/CVE-2007-6399/index.md)
```

## Sources

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

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