View online: https://www.drupal.org/node/2627638
* Advisory ID: DRUPAL-SA-CONTRIB-2015-171 * Project: Token Insert Entity [1] (third-party module) * Version: 7.x * Date: 2015-December-02 * Security risk: 10/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:Default [2] * Vulnerability: Access bypass, Information Disclosure
-------- DESCRIPTION ---------------------------------------------------------
This module offers a WYSIWYG button to embed rendered entities in fields using a WYSIWYG (normally the body of a node).
There is a vulnerability because a user that can create or edit content and has the "insert entity token" permission can insert tokens relating to e.g. an unpublished node and allow any (including anonymous) users to see this rendered node embedded into the main node.
-------- CVE IDENTIFIER(S) ISSUED --------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED ---------------------------------------------------
* Token Insert Entity 7.x-1.x versions prior to 7.x-1.1.
Drupal core is not affected. If you do not use the contributed Token Insert Entity [4] module, there is nothing you need to do.
-------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the Token Insert Entity module for Drupal 7.x, upgrade to Token Insert Entity 7.x-1.1 [5]
Also see the Token Insert Entity [6] project page.
-------- REPORTED BY ---------------------------------------------------------
* killes [7] of the Drupal Security Team
-------- FIXED BY ------------------------------------------------------------
* Juampy NR [8] the module maintainer
-------- COORDINATED BY ------------------------------------------------------
* Peter Wolanin [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/token_insert_entity [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/token_insert_entity [5] https://www.drupal.org/node/2571905 [6] https://www.drupal.org/project/token_insert_entity [7] https://www.drupal.org/user/227 [8] https://www.drupal.org/user/682736 [9] https://www.drupal.org/user/49851 [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