# CVE-2008-2064: Multiple unspecified vulnerabilities in PhpGedView before 4.1.5 have unknown impact and attack vectors related to "a fundamental design flaw


- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1580-1, GHSA-2fr8-3m4g-cvp7

## What is CVE-2008-2064?

CVE-2008-2064 is a critical vulnerability in n/a, published on 2 May 2008. 

### Official description

Multiple unspecified vulnerabilities in PhpGedView before 4.1.5 have unknown impact and attack vectors related to "a fundamental design flaw in the interface (API) to connect phpGedView with external programs like content management systems."

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

It affects 1 product.


Products: Phpgedview Phpgedview.

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

Upgrade to a fixed version.

## Is CVE-2008-2064 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0030](https://insights.sbomify.com/CVE-2004-0030/): Code injection in n/a (critical 9.8)
- [CVE-2005-4469](https://insights.sbomify.com/CVE-2005-4469/): Code injection in n/a (high 7.5)
- [CVE-2004-0031](https://insights.sbomify.com/CVE-2004-0031/): Missing authorization in n/a (high 7.5)
- [CVE-2004-0128](https://insights.sbomify.com/CVE-2004-0128/): Code injection in n/a (high 7.5)
- [CVE-2004-0127](https://insights.sbomify.com/CVE-2004-0127/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2064 is a critical vulnerability in n/a, published on 2 May 2008. 
Exploitation: There is no known exploitation of CVE-2008-2064 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-2008-2064/ (Markdown: https://insights.sbomify.com/CVE-2008-2064/index.md)
```

## Sources

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

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