WordPress - Multiple Vulnerabilities
Summary
DLA-813-1: wordpress - security update. Affects wordpress versions < 3.6.1+dfsg-1~deb7u13. Fixed in 3.6.1+dfsg-1~deb7u13. 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 allow remote attackers to exploit various security weaknesses.
Vulnerability Detail
The following vulnerabilities have been identified in WordPress:
-
CVE-2017-5488: Multiple cross-site scripting (XSS) vulnerabilities in wp-admin/update-core.php in WordPress before 4.7.1 allow remote attackers to inject arbitrary web script or HTML via the name or version header of a plugin.
-
CVE-2017-5489: Cross-site request forgery (CSRF) vulnerability in WordPress before 4.7.1 allows remote attackers to hijack the authentication of unspecified victims via vectors involving a Flash file upload.
-
CVE-2017-5490: Cross-site scripting (XSS) vulnerability in the theme-name fallback functionality in wp-includes/class-wp-theme.php in WordPress before 4.7.1 allows remote attackers to inject arbitrary web script or HTML via a crafted directory name of a theme.
-
CVE-2017-5491: wp-mail.php in WordPress before 4.7.1 might allow remote attackers to bypass intended posting restrictions via a spoofed mail server with the mail.example.com name.
-
CVE-2017-5492: Cross-site request forgery (CSRF) vulnerability in the widget-editing accessibility-mode feature in WordPress before 4.7.1 allows remote attackers to hijack the authentication of unspecified victims for requests that perform a widgets-access action.
-
CVE-2017-5493: wp-includes/ms-functions.php in the Multisite WordPress API in WordPress before 4.7.1 does not properly choose random numbers for keys, which makes it easier for remote attackers to bypass intended access restrictions via a crafted site signup or user signup.
-
CVE-2017-5610: wp-admin/includes/class-wp-press-this.php in Press This in WordPress before 4.7.2 does not properly restrict visibility of a taxonomy-assignment user interface, allowing remote attackers to bypass intended access restrictions by reading terms.
-
CVE-2017-5611: SQL injection vulnerability in wp-includes/class-wp-query.php in WP_Query in WordPress before 4.7.2 allows remote attackers to execute arbitrary SQL commands by leveraging the presence of an affected plugin or theme that mishandles a crafted post type name.
-
CVE-2017-5612: Cross-site scripting (XSS) vulnerability in wp-admin/includes/class-wp-posts-list-table.php in the posts list table in WordPress before 4.7.2 allows remote attackers to inject arbitrary web script or HTML via a crafted excerpt.
How To Fix
Minimum fixed version
3.6.1+dfsg-1~deb7u13
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 has been found to have multiple vulnerabilities that could potentially compromise the security of your website. It is crucial to update your WordPress installation to the latest version and keep all plugins and themes up to date. Regularly monitoring for vulnerabilities using tools like Vulert can help ensure the ongoing security of your WordPress site. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for wordpress →
FAQ
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.
These vulnerabilities could allow remote attackers to inject malicious code, bypass authentication, perform cross-site scripting attacks, and execute arbitrary SQL commands. This can lead to unauthorized access, data theft, and compromise of the affected WordPress site.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your WordPress site is affected by these vulnerabilities. Simply provide the manifest file (e.g., package-lock.json) of your WordPress installation, and Vulert will analyze it for any known vulnerabilities.
At this time, there are no known workarounds for these vulnerabilities. It is recommended to upgrade your WordPress installation to the latest version and keep all plugins and themes up to date.
You can find more information about WordPress security, including best practices and guidelines, on the official WordPress website (https://wordpress.org/support/article/hardening-wordpress/).
Related vulnerabilities
Recent vulnerabilities recorded for wordpress.
