View online: https://www.drupal.org/node/2411573 * Advisory ID: DRUPAL-SA-CONTRIB-2015-026 * Project: Taxonews [1] (third-party module) * Version: 5.x, 6.x, 7.x * Date: 2015-January-21 * Security risk: 13/25 ( Moderately Critical) AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- This module enables you to create blocks of nodes carrying a given taxonomy term. The module doesn't sufficiently escape term names in the blocks it builds leading to a Cross Site Scripting (XSS) vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with the permission "administer taxonomy" or the ability to create terms in some other way. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Taxonews 7.x-1.x versions prior to 7.x-1.1. * Taxonews 6.x-1.x versions prior to 6.x-1.2. Drupal core is not affected. If you do not use the contributed Taxonews [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version of Taxonews module: * For Drupal 7.x, upgrade to Taxonews 7.x-1.1 [5] * For Drupal 6.x, upgrade to Taxonews 6.x-1.2 [6] Also see the Taxonews [7] project page. -------- REPORTED BY --------------------------------------------------------- * Pere Orga [8] provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * FGM [9] the module maintainer -------- COORDINATED BY ------------------------------------------------------ * Pere Orga [10] 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 [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/taxonews [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/taxonews [5] https://www.drupal.org/node/2409769 [6] https://www.drupal.org/node/2409767 [7] https://www.drupal.org/project/taxonews [8] https://www.drupal.org/user/2301194 [9] https://www.drupal.org/user/27985 [10] https://www.drupal.org/user/2301194 [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