high
8.1
CWE
829
Advisory Published
CVE Published
Updated

CVE-2017-6381

First published: Wed Mar 15 2017(Updated: )

A 3rd party development library including with Drupal 8 development dependencies is vulnerable to remote code execution. This is mitigated by the default .htaccess protection against PHP execution, and the fact that Composer development dependencies aren't normal installed. You might be vulnerable to this if you are running a version of Drupal before 8.2.2. To be sure you aren't vulnerable, you can remove the <siteroot>/vendor/phpunit directory from your production deployments

Credit: mlhess@drupal.org mlhess@drupal.org

Affected SoftwareAffected VersionHow to fix
composer/drupal/core>=8.0<8.1.0>=8.1.0<8.2.0>=8.2.0<8.2.7
composer/drupal/drupal>=8.0<8.1.0>=8.1.0<8.2.0>=8.2.0<8.2.7
composer/drupal/drupal>=8.0<8.2.7
8.2.7
composer/drupal/core>=8.0<8.2.7
8.2.7
Drupal=8.0.0
Drupal=8.0.0-alpha10
Drupal=8.0.0-alpha11
Drupal=8.0.0-alpha12
Drupal=8.0.0-alpha13
Drupal=8.0.0-alpha14
Drupal=8.0.0-alpha15
Drupal=8.0.0-alpha2
Drupal=8.0.0-alpha3
Drupal=8.0.0-alpha4
Drupal=8.0.0-alpha5
Drupal=8.0.0-alpha6
Drupal=8.0.0-alpha7
Drupal=8.0.0-alpha8
Drupal=8.0.0-alpha9
Drupal=8.0.0-beta1
Drupal=8.0.0-beta10
Drupal=8.0.0-beta11
Drupal=8.0.0-beta12
Drupal=8.0.0-beta13
Drupal=8.0.0-beta14
Drupal=8.0.0-beta15
Drupal=8.0.0-beta16
Drupal=8.0.0-beta2
Drupal=8.0.0-beta3
Drupal=8.0.0-beta4
Drupal=8.0.0-beta6
Drupal=8.0.0-beta7
Drupal=8.0.0-beta9
Drupal=8.0.0-rc1
Drupal=8.0.0-rc2
Drupal=8.0.0-rc3
Drupal=8.0.0-rc4
Drupal=8.0.1
Drupal=8.0.2
Drupal=8.0.3
Drupal=8.0.4
Drupal=8.0.5
Drupal=8.0.6
Drupal=8.1.0
Drupal=8.1.0-beta1
Drupal=8.1.0-beta2
Drupal=8.1.0-rc1
Drupal=8.1.1
Drupal=8.1.2
Drupal=8.1.3
Drupal=8.1.4
Drupal=8.1.5
Drupal=8.1.6
Drupal=8.1.7
Drupal=8.1.8
Drupal=8.1.9
Drupal=8.1.10
Drupal=8.2.0
Drupal=8.2.0-beta1
Drupal=8.2.0-beta2
Drupal=8.2.0-beta3
Drupal=8.2.0-rc1
Drupal=8.2.0-rc2
Drupal=8.2.1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2017-6381?

    CVE-2017-6381 has a critical severity rating due to its potential for remote code execution.

  • How do I fix CVE-2017-6381?

    To fix CVE-2017-6381, upgrade to Drupal core version 8.2.7 or later.

  • What versions of Drupal are affected by CVE-2017-6381?

    CVE-2017-6381 affects Drupal versions 8.0.x and 8.1.x up to 8.1.10, as well as versions from 8.2.0 up to 8.2.6.

  • What impacts does CVE-2017-6381 pose to my Drupal site?

    If exploited, CVE-2017-6381 allows attackers to execute arbitrary PHP code on the server, potentially compromising the entire site.

  • Is CVE-2017-6381 mitigated by default settings?

    Yes, CVE-2017-6381 is partially mitigated by default .htaccess restrictions that protect against PHP execution.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203