View online: https://www.drupal.org/node/2407315
* Advisory ID: DRUPAL-SA-CONTRIB-2015-015 * Project: Term merge [1] (third-party module) * Version: 7.x * Date: 2015-January-14 * Security risk: 12/25 ( Moderately Critical) AC:Complex/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting
-------- DESCRIPTION ---------------------------------------------------------
This module enables you to merge (synonymous) taxonomy terms among themselves.
The module doesn't sufficiently filter user input under certain conditions, thereby opening a Cross Site Scripting (XSS) vulnerability.
This vulnerability is mitigated by the fact that an attacker must be able to create taxonomy terms.
-------- CVE IDENTIFIER(S) ISSUED --------------------------------------------
* /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./
-------- VERSIONS AFFECTED ---------------------------------------------------
* Term Merge 7.x-1.x versions prior to 7.x-1.2.
Drupal core is not affected. If you do not use the contributed Term merge [4] module, there is nothing you need to do.
-------- SOLUTION ------------------------------------------------------------
Install the latest version:
* If you use the Term Merge module for Drupal 7.x, upgrade to Term Merge 7.x-1.2 [5]
Also see the Term merge [6] project page.
-------- REPORTED BY ---------------------------------------------------------
* Pere Orga [7] provisional member of the Drupal Security Team
-------- FIXED BY ------------------------------------------------------------
* Alexander Trotsenko [8] the module maintainer
-------- COORDINATED BY ------------------------------------------------------
* Pere Orga [9] 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 [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/term_merge [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/term_merge [5] https://www.drupal.org/node/2406869 [6] https://www.drupal.org/project/term_merge [7] https://www.drupal.org/user/2301194 [8] https://www.drupal.org/user/504128 [9] https://www.drupal.org/user/2301194 [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