Drupal custom content type cross-site scripting

drupal-contenttype-xss (35637) The risk level is classified as MediumMedium Risk


Drupal is vulnerable to cross-site scripting, caused by improper validation of user-supplied input by multiple scripts, including the setting.php script. An authenticated remote attacker with "administer content types" permissions could exploit this vulnerability using custom content type name fields to inject malicious script into a Web page which would be executed in a victim's Web browser within the security context of the hosting Web site, once the page is viewed. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.


Base Score: 2.5
  Access Vector: Remote
  Access Complexity: High
  Authentication: Required
  Confidentiality Impact: Partial
  Integrity Impact: Partial
  Availability Impact: None
Temporal Score: 2.2
  Exploitability: High
  Remediation Level: Official-Fix
  Report Confidence: Confirmed


Gain Access


Refer to DRUPAL-SA-2007-018 for patch, upgrade, or suggested workaround information. See References.


  • DRUPAL-SA-2007-018: Drupal core - Multiple cross site scripting vulnerabilities.
  • BID-25097: Drupal Multiple Cross-Site Scripting Vulnerabilities
  • CVE-2007-4064: Multiple cross-site scripting (XSS) vulnerabilities in Drupal 5.x before 5.2, and 4.7.x before 4.7.7, (1) allow remote attackers to inject arbitrary web script or HTML via some server variables
  • SA26224: Drupal Multiple Cross-Site Scripting and Request Forgery Vulnerabilities

Platforms Affected:

  • Drupal Drupal 4.7.x prior to 4.7.7
  • Drupal Drupal 5.x prior to 5.2


Jul 26, 2007

The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.

For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this

Return to the main page