# CVE-2008-5776: Path traversal in n/a

> Remote attackers can execute arbitrary local files or include remote files via directory traversal in Aperto Blog parameters.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w2cc-c38q-h9rw

## What is CVE-2008-5776?

CVE-2008-5776 is a high-severity path traversal vulnerability in n/a, published on 30 Dec 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in Aperto Blog 0.1.1 allow remote attackers to include and execute arbitrary local files via directory traversal sequences in the (1) action parameter to admin.php and the (2) get parameter to index.php.  NOTE: in some environments, this can be leveraged for remote file inclusion by using a UNC share pathname or an ftp, ftps, or ssh2.sftp URL.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Apertoblog Apertoblog.

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

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

## Is CVE-2008-5776 being exploited?

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

Public exploit code:

- Aperto Blog 0.1.1 - Local File Inclusion / SQL Injection (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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