CVE-2016-5839 Security feature bypass in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2016-5839 and fix it if it is affected.
What it is: CVE-2016-5839 is a high-severity vulnerability in Wordpress Wordpress, published on 29 Jun 2016. 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-2016-5839 in the wild and no public exploit code.
Affected product: Wordpress Wordpress. 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-2016-5839/ (Markdown: https://insights.sbomify.com/CVE-2016-5839/index.md)
Remote attackers can bypass WordPress file name sanitization protections, potentially allowing malicious file uploads or other security circumventions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2016-5839?
CVE-2016-5839 is a high-severity vulnerability in Wordpress Wordpress, published on 29 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
WordPress before 4.5.3 allows remote attackers to bypass the sanitize_file_name protection mechanism via unspecified vectors.
Which versions are affected by CVE-2016-5839?
It affects 1 product.
Products include Wordpress Wordpress.
How do I fix CVE-2016-5839?
Upgrade to a fixed version.
Is CVE-2016-5839 being exploited?
There is no known exploitation of CVE-2016-5839 in the wild and no public exploit code.
Other vulnerabilities in Wordpress Wordpress
Sources
Also known as DEBIAN-CVE-2016-5839, GHSA-6jm4-p692-pwq2, UBUNTU-CVE-2016-5839.