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

> Remote attackers can obtain sensitive system information by directly accessing the phpinfo.php file in YourPlace.

- **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:** 29 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7j8v-9pgr-crvw

## What is CVE-2008-6771?

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

### Official description

YourPlace 1.0.2 and earlier allows remote attackers to obtain sensitive system information via a direct request via a direct request to user/uploads/phpinfo.php, which calls the phpinfo function.

Weakness: CWE-264

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

It affects 1 product.


Products: Peterselie Yourplace.

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

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

## Is CVE-2008-6771 being exploited?

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

Public exploit code:

- yourplace 1.0.2 - Multiple Vulnerabilities / Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6772](https://insights.sbomify.com/CVE-2008-6772/): Business logic in n/a (high 7.5)
- [CVE-2008-6773](https://insights.sbomify.com/CVE-2008-6773/): Code injection in n/a (medium 6.5)
- [CVE-2008-6769](https://insights.sbomify.com/CVE-2008-6769/): File upload in n/a (medium 6.0)
- [CVE-2008-6770](https://insights.sbomify.com/CVE-2008-6770/): Information disclosure in n/a (medium 5.0)
- [CVE-2008-6774](https://insights.sbomify.com/CVE-2008-6774/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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