CVE-2008-6681: Cross-Site Scripting in dojo

dojo Updated 02 Oct 2025

Summary

01/09/2020
Yes i
Moderate
Not published

CVE-2008-6681: Cross-Site Scripting in dojo. Affects dojo versions < 1.1.0. Fixed in 1.1.0. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Dojo is an open-source JavaScript toolkit that provides a comprehensive set of features for building web applications. It includes various components, such as dijit.Editor and textarea, which allow users to input and edit text. These components execute the contents as JavaScript, even when sanitized, making them vulnerable to cross-site scripting (XSS) attacks.

Vulnerability Detail

The affected versions of dojo, specifically versions <= 1.0, are susceptible to a cross-site scripting vulnerability. This vulnerability allows an attacker to inject malicious scripts into the dijit.Editor and textarea components, which will be executed by the browser. Even if the input is sanitized, the components still execute the contents as JavaScript, enabling the execution of arbitrary code on the user's browser. This can lead to various security risks, such as session hijacking, data theft, or unauthorized actions on behalf of the user.

How To Fix

Latest published version: 1.17.3 as of 23 Oct 2026

npm install dojo@1.17.3

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.1.0

This is the first release that contains the fix.

npm install dojo@1.1.0

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

Workaround

There is no specific workaround mentioned for this vulnerability. However, as a general best practice, it is recommended to implement input validation and output encoding to prevent XSS attacks. Additionally, web developers can use Content Security Policy (CSP) headers to restrict the execution of scripts from external sources.

Conclusion

In conclusion, the dojo package is vulnerable to a cross-site scripting (XSS) attack in the dijit.Editor and textarea components. To mitigate this vulnerability, it is crucial to update to version 1.1 or later. Implementing input validation, output encoding, and Content Security Policy (CSP) headers can further enhance the security of web applications. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for dojo →

Share this vulnerability

FAQ

Cross-site scripting (XSS) is a type of security vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users. These scripts can be used to steal sensitive information, manipulate web content, or perform unauthorized actions on behalf of the user.

This vulnerability affects the dijit.Editor and textarea components in dojo. These components execute user input as JavaScript, even when sanitized, making them vulnerable to XSS attacks. An attacker can exploit this vulnerability to inject and execute malicious scripts on the user's browser.

The consequences of this vulnerability can vary depending on the attacker's intentions. It can lead to session hijacking, where the attacker gains unauthorized access to a user's session. It can also result in data theft, where sensitive information entered in the affected components is captured by the attacker. Furthermore, the attacker can perform unauthorized actions on behalf of the user, potentially causing damage or compromising the user's privacy.

No, only versions of dojo <= 1.0 are affected by this vulnerability. Updating to version 1.1 or later will address the issue and protect against this vulnerability.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the package-lock.json file. It provides a simple way to assess the security of your application without requiring access to the code or installation.

Related vulnerabilities

Recent vulnerabilities recorded for dojo.

How To Fix

Latest published version: 1.17.3 as of 23 Oct 2026

npm install dojo@1.17.3

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.1.0

This is the first release that contains the fix.

npm install dojo@1.1.0

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