View online: https://www.drupal.org/node/2507605 * Advisory ID: DRUPAL-SA-CONTRIB-2015-120 * Project: Inline Entity Form [1] (third-party module) * Version: 7.x * Date: 2015-June-17 * Security risk: 7/25 ( Less Critical) AC:Basic/A:Admin/CI:None/II:None/E:Theoretical/TD:All [2] * Vulnerability: Cross Site Scripting -------- DESCRIPTION --------------------------------------------------------- The Inline Entity Form module provides a field widget for inline management (creation, modification, removal) of referenced entities. The module doesn't sufficiently sanitize user supplied text, thereby exposing a Cross Site Scripting vulnerability. This vulnerability is mitigated by the fact that an attacker must have a role with permission to create/edit fields. -------- CVE IDENTIFIER(S) ISSUED -------------------------------------------- * /A CVE identifier [3] will be requested, and added upon issuance, in accordance with Drupal Security Team processes./ -------- VERSIONS AFFECTED --------------------------------------------------- * Inline Entity Form 7.x-1.x versions prior to 7.x-1.6. Drupal core is not affected. If you do not use the contributed Inline Entity Form [4] module, there is nothing you need to do. -------- SOLUTION ------------------------------------------------------------ Install the latest version: * If you use the Inline Entity Form module for Drupal 7.x, upgrade to Inline Entity Form 7.x-1.6 [5] Also see the Inline Entity Form [6] project page. -------- REPORTED BY --------------------------------------------------------- * Matt Vance [7], provisional member of the Drupal Security Team -------- FIXED BY ------------------------------------------------------------ * Matt Vance [8], 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 [9]. Learn more about the Drupal Security team and their policies [10], writing secure code for Drupal [11], and securing your site [12]. Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [13] [1] https://www.drupal.org/project/inline_entity_form [2] https://www.drupal.org/security-team/risk-levels [3] http://cve.mitre.org/ [4] https://www.drupal.org/project/inline_entity_form [5] https://www.drupal.org/node/2507593 [6] https://www.drupal.org/project/inline_entity_form [7] https://www.drupal.org/user/88338 [8] https://www.drupal.org/user/88338 [9] https://www.drupal.org/contact [10] https://www.drupal.org/security-team [11] https://www.drupal.org/writing-secure-code [12] https://www.drupal.org/security/secure-configuration [13] https://twitter.com/drupalsecurity