CVE-2016-9836
First published: Mon Dec 05 2016(Updated: )
The file scanning mechanism of JFilterInput::isFileSafe() in Joomla! CMS before 3.6.5 does not consider alternative PHP file extensions when checking uploaded files for PHP content, which enables a user to upload and execute files with the `.php6`, `.php7`, `.phtml`, and `.phpt` extensions. Additionally, JHelperMedia::canUpload() did not blacklist these file extensions as uploadable file types.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Joomla | <=3.6.4 |
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-9836?
CVE-2016-9836 has high severity due to its potential for allowing unauthorized file uploads and execution.
How do I fix CVE-2016-9836?
To fix CVE-2016-9836, upgrade Joomla! CMS to version 3.6.5 or later.
What are the vulnerable file extensions in CVE-2016-9836?
CVE-2016-9836 affects file uploads with extensions like .php6, .php7, .phtml, and .phpt.
Which versions of Joomla! are affected by CVE-2016-9836?
CVE-2016-9836 affects Joomla! versions up to and including 3.6.4.
What type of vulnerability is CVE-2016-9836?
CVE-2016-9836 is a file upload vulnerability that allows execution of potentially malicious scripts.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/last-modified-date
- agent/author
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/joomla
- canonical/joomla
- version/joomla/3.6.4