CVE-2018-6389: High severity WordPress vulnerability

Published Feb 6, 2018
·
Updated

In WordPress through 4.9.2, unauthenticated attackers can cause a denial of service (resource consumption) by using the large list of registered .js files (from wp-includes/script-loader.php) to construct a series of requests to load every file many times.

Affected Software

1 affected component
WordPress<=4.9.2

Event History

Feb 6, 2018
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2018-6389?

CVE-2018-6389 is categorized as a denial of service vulnerability, caused by unauthenticated attackers due to resource consumption.

2

How do I fix CVE-2018-6389?

To mitigate CVE-2018-6389, update your WordPress installation to a version later than 4.9.2.

3

Who is affected by CVE-2018-6389?

CVE-2018-6389 affects unprotected installations of WordPress versions up to 4.9.2.

4

What type of attack does CVE-2018-6389 involve?

CVE-2018-6389 involves a denial of service attack that consumes server resources by repeatedly loading registered .js files.

5

Can CVE-2018-6389 be exploited remotely?

Yes, attackers can exploit CVE-2018-6389 remotely without authentication.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203