# CVE-2005-3049: Information disclosure in n/a

> Remote attackers can access sensitive tracking data by requesting predictable filenames stored under the web root in PhpMyFaq.

- **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:** 23 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rxch-49p9-53hx

## What is CVE-2005-3049?

CVE-2005-3049 is a medium-severity 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

PhpMyFaq 1.5.1 stores data files under the web document root with insufficient access control and predictable filenames, which allows remote attackers to obtain sensitive information via a direct request to the data/tracking[DATE] file.

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

It affects 1 product.


Products: Phpmyfaq Phpmyfaq.

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

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

## Is CVE-2005-3049 being exploited?

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

## 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-3049 and fix it if it is affected.

What it is: CVE-2005-3049 is a medium-severity 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: There is no known exploitation of CVE-2005-3049 in the wild and no public exploit code.

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

## Sources

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

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