WordPress - Multiple Vulnerabilities
Summary
DLA-1151-1: wordpress - security update. Affects wordpress versions < 3.6.1+dfsg-1~deb7u17. Fixed in 3.6.1+dfsg-1~deb7u17. 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 compromise the security of the platform and the websites running on it.
Vulnerability Detail
The following vulnerabilities have been identified in WordPress:
-
Cross-Domain Flash Injection (CVE-2016-9263): When domain-based flashmediaelement.swf sandboxing is not used, remote attackers can conduct cross-domain Flash injection attacks by leveraging code contained within the wp-includes/js/mediaelement/flashmediaelement.swf file. This issue has been resolved by completely removing flashmediaelement.swf.
-
Cross-Site Scripting (XSS) in Link Modal (CVE-2017-14718): WordPress is susceptible to a Cross-Site Scripting attack in the link modal via a javascript: or data: URL.
-
Directory Traversal in ZipArchive and PclZip Components (CVE-2017-14719): WordPress is vulnerable to a directory traversal attack during unzip operations in the ZipArchive and PclZip components.
-
Cross-Site Scripting (XSS) in Template List View (CVE-2017-14720): WordPress allows a Cross-Site Scripting attack in the template list view via a crafted template name.
-
Cross-Site Scripting (XSS) in Plugin Editor (CVE-2017-14721): WordPress allows Cross-Site Scripting in the plugin editor via a crafted plugin name.
-
Directory Traversal in Customizer Component (CVE-2017-14722): WordPress allows a Directory Traversal attack in the Customizer component via a crafted theme filename.
-
SQL Injection in $wpdb->prepare (CVE-2017-14723): WordPress mishandles % characters and additional placeholder values in $wpdb->prepare, which may enable SQL injection attacks.
-
Open Redirect in wp-admin/user-edit.php (CVE-2017-14725): WordPress is susceptible to an open redirect attack in wp-admin/user-edit.php.
-
Cleartext Storage of Activation Keys (CVE-2017-14990): WordPress stores cleartext wp_signups.activation_key values, which might make it easier for remote attackers to hijack unactivated user accounts by leveraging database read access.
These vulnerabilities pose various risks, including unauthorized code execution, data manipulation, and account hijacking.
How To Fix
Minimum fixed version
3.6.1+dfsg-1~deb7u17
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 →
Workaround
There are no known workarounds for these vulnerabilities. It is crucial to apply the recommended security update to ensure the protection of your WordPress installation and the websites hosted on it.
Conclusion
WordPress has been found to have multiple vulnerabilities that could potentially compromise the security of websites running on the platform. It is crucial to apply the recommended security update to mitigate these risks. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for wordpress →
FAQ
You can use the Vulert Playground (https://vulert.com/scanner) to check if your WordPress installation is affected by these vulnerabilities. Simply upload your package-lock.json file and the Vulert Playground will analyze it for any known vulnerabilities.
While specific exploits for these vulnerabilities have not been disclosed publicly, it is important to apply the security update as soon as possible to mitigate the risk of potential attacks.
No, manually removing the flashmediaelement.swf file is not recommended. It is best to apply the official security update, which completely removes the vulnerable file and provides additional security enhancements.
While the security update addresses the identified vulnerabilities in the core WordPress installation, it is also recommended to update all plugins and themes to their latest versions. This helps ensure that any potential vulnerabilities in third-party components are also patched.
You can visit the official WordPress website (https://wordpress.org) for more information about security updates, best practices, and guidelines for securing your WordPress installation.
Related vulnerabilities
Recent vulnerabilities recorded for wordpress.
