CVE-2016-5839
First published: Wed Jun 29 2016(Updated: )
WordPress before 4.5.3 allows remote attackers to bypass the sanitize_file_name protection mechanism via unspecified vectors.
Credit: security@debian.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | <=4.5.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-5839?
CVE-2016-5839 has been classified as a medium severity vulnerability.
How do I fix CVE-2016-5839?
To fix CVE-2016-5839, upgrade WordPress to version 4.5.3 or later.
What type of vulnerability is CVE-2016-5839?
CVE-2016-5839 is a security vulnerability that allows for bypassing of sanitization controls.
Who is affected by CVE-2016-5839?
CVE-2016-5839 affects all WordPress installations prior to version 4.5.3.
Can CVE-2016-5839 be exploited remotely?
Yes, CVE-2016-5839 can be exploited by remote attackers.
- agent/type
- agent/softwarecombine
- agent/author
- agent/references
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/wordpress
- canonical/wordpress
- version/wordpress/4.5.2