View online: https://www.drupal.org/node/2553971 * Advisory ID: DRUPAL-SA-CONTRIB-2015-139 * Project: Workbench Email [1] (third-party module) * Version: 7.x * Date: 2015-August-19 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:User/CI:None/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- Workbench Email module provides a way for administrators to define email transitions and configurable email subject / messages between those transitions. The module causes node and field validations to be skipped when saving nodes. The vulnerability is mitigated by the fact that an attacker must have a role with permission to create or update nodes. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Workbench Email 7.x-3.x versions prior to 7.x-3.4 Drupal core is not affected. If you do not use the contributed Workbench Email [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Workbench Email module for Drupal 7.x, upgrade to Workbench Email 7.x-3.4 [5] Also see the Workbench Email [6] project page. -------- REPORTED BY --------------------------------------------------------- * Yves Chedemois [7] -------- FIXED BY ------------------------------------------------------------ * Brandon Tate [8] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere orga [9] of the Drupal Security Team -------- CONTACT AND MORE INFORMATION ---------------------------------------- The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact [10]. Learn more about the Drupal Security team and their policies [11], writing secure code for Drupal [12], and securing your site [13]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [14] [1] https://www.drupal.org/project/workbench_email [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/workbench_email [5] https://www.drupal.org/node/2484229 [6] https://www.drupal.org/project/workbench_email [7] https://www.drupal.org/u/yched [8] https://www.drupal.org/u/teknic [9] https://www.drupal.org/u/pere-orga [10] https://www.drupal.org/contact [11] https://www.drupal.org/security-team [12] https://www.drupal.org/writing-secure-code [13] https://www.drupal.org/security/secure-configuration [14] https://twitter.com/drupalsecurity