# CVE-2005-3048: Path traversal in n/a

> Remote attackers can read arbitrary files and execute code via path traversal in the LANGCODE parameter of PhpMyFaq.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 23 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4447-hm8w-ggf7

## What is CVE-2005-3048?

CVE-2005-3048 is a medium-severity path traversal vulnerability in Phpmyfaq Phpmyfaq, published on 23 Sep 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php in PhpMyFaq 1.5.1 allows remote attackers to read arbitrary files or include arbitrary PHP files via a .. (dot dot) in the LANGCODE parameter, which also allows direct code injection via the User Agent field in a request packet, which can be activated by using LANGCODE to reference the user tracking data file.

## Which versions are affected by CVE-2005-3048?

It affects 1 product.


Products: Phpmyfaq Phpmyfaq.

## How do I fix CVE-2005-3048?

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

## Is CVE-2005-3048 being exploited?

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

Public exploit code:

- phpMyFAQ 1.5.1 - 'User-Agent' Remote Shell Injection (exploitdb)

## Other vulnerabilities in Phpmyfaq Phpmyfaq

- [CVE-2023-0310](https://insights.sbomify.com/CVE-2023-0310/): Cross-site Scripting (XSS) - Stored in thorsten/phpmyfaq (critical 9.8)
- [CVE-2022-4407](https://insights.sbomify.com/CVE-2022-4407/): Cross-site Scripting (XSS) - Reflected in thorsten/phpmyfaq (critical 9.8)
- [CVE-2017-11187](https://insights.sbomify.com/CVE-2017-11187/): Security feature bypass in n/a (critical 9.8)
- [CVE-2026-76213](https://insights.sbomify.com/CVE-2026-76213/): phpMyFAQ before 4.1.7 2FA Brute-Force via Session-Scoped Throttle (critical 9.1)
- [CVE-2026-76214](https://insights.sbomify.com/CVE-2026-76214/): phpMyFAQ before 4.1.7 WebAuthn Replay Attack via Challenge (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3048 and fix it if it is affected.

What it is: CVE-2005-3048 is a medium-severity path traversal vulnerability in Phpmyfaq Phpmyfaq, published on 23 Sep 2005. 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-2005-3048 exists.

Affected product: Phpmyfaq Phpmyfaq. 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-2005-3048/ (Markdown: https://insights.sbomify.com/CVE-2005-3048/index.md)
```

## Sources

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

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