CVE-2006-6186 Multiple directory traversal vulnerabilities in enomphp 4.0 allow remote attackers to read arbitrary files via a ..
Medium 5.0
Published
Updated
Check this codebase for CVE-2006-6186 and fix it if it is affected.
What it is: CVE-2006-6186 is a medium-severity vulnerability in n/a, published on 1 Dec 2006.
Exploitation: There is no known exploitation of CVE-2006-6186 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-2006-6186/ (Markdown: https://insights.sbomify.com/CVE-2006-6186/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2006-6186?
CVE-2006-6186 is a medium-severity vulnerability in n/a, published on 1 Dec 2006.
Official description
Multiple directory traversal vulnerabilities in enomphp 4.0 allow remote attackers to read arbitrary files via a .. (dot dot) in the dir parameter to (1) config.php, (2) ranklv_inside.php, (3) rankml_inside.php, and (4) admin/Restore/config.php.
Which versions are affected by CVE-2006-6186?
It affects 1 product.
Products include Enomphp Enomphp.
How do I fix CVE-2006-6186?
No fix has been published for CVE-2006-6186 yet. Limit exposure of the affected software until one is available.
Is CVE-2006-6186 being exploited?
There is no known exploitation of CVE-2006-6186 in the wild and no public exploit code.
Sources
Also known as GHSA-wh7h-cj5p-f7mp.