WordPress - Multiple Vulnerabilities
Summary
DLA-1151-2: wordpress - regression update. Affects wordpress versions < 3.6.1+dfsg-1~deb7u19. Fixed in 3.6.1+dfsg-1~deb7u19. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
WordPress is a popular web blogging tool used for creating and managing websites. It provides a user-friendly interface and a wide range of features for content creation and customization. However, several vulnerabilities have been discovered in WordPress, which could potentially be exploited by attackers to compromise the security of the system.
Vulnerability Detail
The following vulnerabilities have been identified in WordPress:
-
CVE-2016-9263: This vulnerability allows remote attackers to conduct cross-domain Flash injection attacks by leveraging code contained within the wp-includes/js/mediaelement/flashmediaelement.swf file. The issue has been resolved by completely removing flashmediaelement.swf.
-
CVE-2017-14718: WordPress is susceptible to a Cross-Site Scripting attack in the link modal via a javascript: or data: URL.
-
CVE-2017-14719: WordPress is vulnerable to a directory traversal attack during unzip operations in the ZipArchive and PclZip components.
-
CVE-2017-14720: WordPress allows a Cross-Site scripting attack in the template list view via a crafted template name.
-
CVE-2017-14721: WordPress allows Cross-Site scripting in the plugin editor via a crafted plugin name.
-
CVE-2017-14722: WordPress allows a Directory Traversal attack in the Customizer component via a crafted theme filename.
-
CVE-2017-14723: WordPress mishandles % characters and additional placeholder values in $wpdb->prepare, which could enable SQL injection attacks.
-
CVE-2017-14725: WordPress is susceptible to an open redirect attack in wp-admin/user-edit.php.
-
CVE-2017-14990: WordPress stores cleartext wp_signups.activation_key values, making it easier for remote attackers to hijack unactivated user accounts.
These vulnerabilities pose a risk to the confidentiality, integrity, and availability of the WordPress installation. Attackers could potentially execute arbitrary code, steal sensitive information, or manipulate the website's content.
How To Fix
Minimum fixed version
3.6.1+dfsg-1~deb7u19
This is the first release that contains the fix.
sudo apt-get install --only-upgrade wordpressTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
WordPress is a widely used web blogging tool that has been found to have multiple vulnerabilities. These vulnerabilities could potentially be exploited by attackers to compromise the security of WordPress installations. It is highly recommended to upgrade WordPress to the latest version and apply all available security patches to mitigate the risk. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for wordpress →
FAQ
These vulnerabilities could allow attackers to execute arbitrary code, conduct cross-site scripting attacks, perform directory traversal attacks, and hijack user accounts.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your WordPress installation is affected by these vulnerabilities. Simply provide the manifest file (e.g., package-lock.json) and Vulert will analyze it for potential vulnerabilities.
At this time, there are no known workarounds for these vulnerabilities. It is recommended to upgrade WordPress to the latest version and apply all available security patches.
Yes, these vulnerabilities can be exploited remotely by attackers who have access to the affected WordPress installation.
There have been reports of active exploitation of some of these vulnerabilities in the wild. It is crucial to update WordPress as soon as possible to mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for wordpress.
