View online: https://www.drupal.org/node/2789421 * Advisory ID: DRUPAL-SA-CONTRIB-2016-049 * Project: Workbench Scheduler [1] (third-party module) * Version: 7.x * Date: 2016-August-24 * Security risk: 13/25 ( Moderately Critical) AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- Workbench Scheduler module provides users with the ability to create schedules that change moderated content from one workbench moderation state to another. An authenticated user could add a schedule to a node even when that content type has schedules disabled. The vulnerability is mitigated by the fact that a attacker must have access to an account in the system with permission to edit content and create schedules. Also, only sites with a specific combination of permissions and modules are affected. -------- 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 Scheduler 7.x-1.x versions prior to 7.x-1.9. Drupal core is not affected. If you do not use the contributed Workbench Scheduler [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Workbench Scheduler module for Drupal 7.x, upgrade to Workbench Scheduler 7.x-1.9 [5] Also see the Workbench Scheduler [6] project page. -------- REPORTED BY --------------------------------------------------------- * Caroline Boyden [7] -------- FIXED BY ------------------------------------------------------------ * Caroline Boyden [8] * Joshua Bolduc [9], the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [10] 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 [11]. Learn more about the Drupal Security team and their policies [12], writing secure code for Drupal [13], and securing your site [14]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [15] [1] https://www.drupal.org/project/workbench_scheduler [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/workbench_scheduler [5] https://www.drupal.org/project/workbench_scheduler/releases/7.x-1.9 [6] https://www.drupal.org/project/workbench_scheduler [7] https://www.drupal.org/user/657902 [8] https://www.drupal.org/user/657902 [9] https://www.drupal.org/user/1386490 [10] https://www.drupal.org/u/pere-orga [11] https://www.drupal.org/contact [12] https://www.drupal.org/security-team [13] https://www.drupal.org/writing-secure-code [14] https://www.drupal.org/security/secure-configuration [15] https://twitter.com/drupalsecurity