CVE-2005-0613 File upload in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2005-0613 and fix it if it is affected.
What it is: CVE-2005-0613 is a medium-severity vulnerability in n/a, published on 3 Mar 2005. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0613 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-0613/ (Markdown: https://insights.sbomify.com/CVE-2005-0613/index.md)
Remote attackers can upload arbitrary files via FCKeditor in PHP-Nuke, potentially leading to code execution.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2005-0613?
CVE-2005-0613 is a medium-severity vulnerability in n/a, published on 3 Mar 2005. It can be exploited over the network, with no action from the victim.
Official description
Unknown vulnerability in FCKeditor 2.0 RC2, when used with PHP-Nuke, allows remote attackers to upload arbitrary files.
Which versions are affected by CVE-2005-0613?
It affects 1 product.
Products include Fckeditor Fckeditor.
How do I fix CVE-2005-0613?
No fix has been published for CVE-2005-0613 yet. Limit exposure of the affected software until one is available.
Is CVE-2005-0613 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0613 exists.
Public exploit code: 2 Exploit-DB entries.
Other vulnerabilities in n/a
Sources
Also known as GHSA-mch6-c5jx-fv9f.