How severe is CVE-2008-6681?

No CVSS score has been assigned to CVE-2008-6681 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2008-6681?

CVE-2008-6681 affects the following packages: dojo (npm). Ecosystems affected: npm.

How do I fix CVE-2008-6681?

Update dojo to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2008-6681 is resolved across your whole dependency graph.

How do I detect CVE-2008-6681 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dojo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2008-6681 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2008-6681 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2008-6681, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2008-6681?

CVE-2008-6681 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2008-6681?

CVE-2008-6681 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2008-6681 published, and has it been updated?

CVE-2008-6681 was published on September 1, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2008-6681 — dojo

CVE-2008-6681 is a Cross-site Scripting (XSS) vulnerability in dojo. 1 public exploit reference exists, so weaponization risk is real. A fix is available for dojo — see the affected versions and patch details below.

Cross-Site Scripting in dojo

Published

Sep 1, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

31other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

dojonpm

27Kdownloads / week

Description

Affected versions of dojo are susceptible to a cross-site scripting vulnerability in the dijit.Editor and textarea components, which execute their contents as Javascript, even when sanitized.

Recommendation

Update to version 1.1.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`dojo`	all versions	1.1.0`npm install dojo@1.1.0`

Affected Products

1 product · 12 configurations

Application

dojodojotoolkit

≤ 1.0

11 versions

0.1.00.2.00.2.10.2.20.3.00.3.10.4.00.4.10.4.20.4.30.9.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Cross-site scripting (XSS) vulnerability in dijit.Editor in Dojo before …

dojotoolkit.orgNVDAug 2017

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dojo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dojo to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2008-6681 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Affected versions of `dojo` are susceptible to a cross-site scripting vulnerability in the `dijit.Editor` and `textarea` components, which execute their contents as Javascript, even when sanitized. ## Recommendation Update to version 1.1.0 or later.

O3 Security · Impact-Aware SCA

Is CVE-2008-6681 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works