CVE-2005-3307 Directory traversal vulnerability in index.php for FlatNuke 2.5.6 allows remote attackers to read arbitrary files via ".." sequences in the
Medium 5.0
Published
Updated
Check this codebase for CVE-2005-3307 and fix it if it is affected.
What it is: CVE-2005-3307 is a medium-severity vulnerability in n/a, published on 25 Oct 2005.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3307 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-2005-3307/ (Markdown: https://insights.sbomify.com/CVE-2005-3307/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2005-3307?
CVE-2005-3307 is a medium-severity vulnerability in n/a, published on 25 Oct 2005.
Official description
Directory traversal vulnerability in index.php for FlatNuke 2.5.6 allows remote attackers to read arbitrary files via ".." sequences in the (1) user parameter in a profile operation or (2) quale parameter in a newtopic operation.
Which versions are affected by CVE-2005-3307?
How do I fix CVE-2005-3307?
No fix has been published for CVE-2005-3307 yet. Limit exposure of the affected software until one is available.
Is CVE-2005-3307 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3307 exists.
Public exploit code: 1 Exploit-DB entry.
Sources
Also known as GHSA-wrrm-v4f3-7p8w.