View online: https://www.drupal.org/node/2785687 * Advisory ID: DRUPAL-SA-CONTRIB-2014-048 * Project: Panelizer [1] (third-party module) * Version: 7.x * Date: 2016-August-17 * Security risk: 12/25 ( Moderately Critical) AC:None/A:User/CI:None/II:Some/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass -------- DESCRIPTION --------------------------------------------------------- Panelizer enables you to use Panels to replace the display of any entity, and even modify the Panels configuration in-place using the Panels In-Place Editor (IPE). The default behavior for Panels IPE is to allow any user with the permissions "Use the Panels In-Place Editor" and "Change layouts with the Panels In-Place Editor " access to the IPE regardless of whether or not a user has access to edit the underlying entity. While users cannot edit the entity itself, they can change the layout and the different panel panes shown (effectively allowing them to edit it). This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Use the Panels In-Place Editor" and the IPE must be enabled for the specific content type. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Panelizer 7.x-3.x versions prior to 7.x-3.3. Drupal core is not affected. If you do not use the contributed Panelizer [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Panelizer module for Drupal 7.x, upgrade to Panelizer 7.x-3.3 [5] Also see the Panelizer [6] project page. -------- REPORTED BY --------------------------------------------------------- * Branden Hamilton [7] * Joep Hendrix [8] -------- FIXED BY ------------------------------------------------------------ * Jakob Perry [9] the module maintainer * Damien Mckenna [10] * Mike Potter [11] provisional member of the Drupal Security Team * David Snopek [12] of the Drupal Security Team -------- COORDINATED BY ------------------------------------------------------ * Mike Potter [13] provisional member 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 [14]. Learn more about the Drupal Security team and their policies [15], writing secure code for Drupal [16], and securing your site [17]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [18] [1] https://www.drupal.org/project/panelizer [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/panelizer [5] https://www.drupal.org/project/panelizer/releases/7.x-3.3 [6] https://www.drupal.org/project/panelizer [7] https://www.drupal.org/u/brandenlhamilton [8] https://www.drupal.org/u/joep.hendrix [9] https://www.drupal.org/u/japerry [10] https://www.drupal.org/u/damienmckenna [11] https://www.drupal.org/u/mpotter [12] https://www.drupal.org/u/dsnopek [13] https://www.drupal.org/u/mpotter [14] https://www.drupal.org/contact [15] https://www.drupal.org/security-team [16] https://www.drupal.org/writing-secure-code [17] https://www.drupal.org/security/secure-configuration [18] https://twitter.com/drupalsecurity