CVE-2008-3218: Drupal vulnerable to Cross-site Scripting

drupal/drupal Updated 02 Oct 2025

Summary

01/05/2022
Yes i
Moderate
Not published

CVE-2008-3218: Drupal vulnerable to Cross-site Scripting. Affects drupal/drupal versions >= 6.0, < 6.3. Fixed in 6.3. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Drupal is a popular open-source content management system (CMS) written in PHP. It provides a flexible platform for building websites and applications. Drupal allows users to create and manage content, customize the appearance, and extend functionality through modules. However, versions of Drupal 6.x prior to 6.3 are susceptible to multiple cross-site scripting (XSS) vulnerabilities.

Vulnerability Detail

The identified vulnerabilities in Drupal 6.x versions before 6.3 allow remote attackers to inject arbitrary web script or HTML. The first vulnerability is related to free tagging taxonomy terms, which are not properly handled on node preview pages. The second vulnerability involves unspecified OpenID values. Exploiting these vulnerabilities can lead to the execution of malicious code or the manipulation of website content.

How To Fix

Minimum fixed version

6.3

This is the first release that contains the fix.

composer require drupal/drupal:6.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, website administrators can implement input validation and sanitization measures to mitigate the risk of XSS attacks. This can involve implementing strict input filtering, encoding user-generated content, and utilizing security modules or plugins specifically designed to prevent XSS vulnerabilities.

Conclusion

Drupal versions prior to 6.3 are vulnerable to cross-site scripting (XSS) attacks. It is essential for website administrators to upgrade to the latest version of Drupal and apply the necessary security patches to mitigate the risk of exploitation. Regularly monitoring for vulnerabilities and following best practices for secure coding can help maintain the security of Drupal installations. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for drupal/drupal →

Share this vulnerability

FAQ

Drupal is an open-source content management system (CMS) used for building websites and applications. It provides a flexible platform for managing and publishing content.

Cross-site scripting (XSS) vulnerabilities allow attackers to inject malicious scripts into web pages viewed by other users. This can lead to the execution of arbitrary code, theft of sensitive information, or manipulation of website content.

The Drupal vulnerability can be exploited by remote attackers who inject malicious web scripts or HTML into the affected Drupal installation. This can be done through various vectors, such as manipulating free tagging taxonomy terms or exploiting OpenID values.

The Drupal vulnerability can result in the execution of arbitrary code or the manipulation of website content. This can lead to unauthorized access, data theft, defacement, or other malicious activities.

To protect your Drupal installation, it is crucial to keep the software up to date by applying the latest security patches and updates. Additionally, implementing input validation and sanitization measures, utilizing security modules, and following best practices for secure coding can help mitigate the risk of XSS vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for drupal/drupal.

How To Fix

Minimum fixed version

6.3

This is the first release that contains the fix.

composer require drupal/drupal:6.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback