dbcve.org
Dojo ToolkitApplication

CVE-2007-2376

MEDIUM · 5.0 CVSS v2.0 Published 2007-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Dojo framework exchanges data using JavaScript Object Notation (JSON) without an associated protection scheme, which allows remote attackers to obtain the data via a web page that retrieves the data through a URL in the SRC attribute of a SCRIPT element and captures the data using other JavaScript code, aka "JavaScript Hijacking."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Dojo framework exchanges JSON data without protection schemes, allowing remote attackers to steal data via JavaScript hijacking. Attackers embed a SCRIPT tag with the target JSON endpoint as the SRC attribute; when a victim's browser loads and executes the script, the JSON data is captured by attacker-controlled JavaScript code.

MitigationImplement CSRF tokens or request origin validation (Referer/Origin header checks) for JSON endpoints, and consider using POST instead of GET for sensitive JSON responses to prevent cross-origin data theft.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dojo ToolkitApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Dojo Toolkit installation
    Search for dojo.js file in the web application directory or JavaScript libraries folder. Common paths include /js/dojo/, /lib/dojo/, or bundled within scripts/. Check package.json or script tags referencing 'dojo' namespace.
    Affected if Dojo Toolkit is present in the application
  2. Identify JSON-producing endpoints using Dojo
    Search codebase for Dojo XHR functions such as dojo.xhrGet, dojo.xhrPost, dojo.request.get, or dojo.json for exchanging JSON data. Review application URL patterns that return JSON responses.
    Affected if Application uses Dojo to exchange JSON data via AJAX requests
  3. Verify endpoint accepts GET requests for JSON
    Test suspected JSON endpoints with a GET request (for example, using curl -X GET or browser DevTools). Check if the endpoint returns JSON data without requiring authentication or CSRF tokens.
    Affected if JSON endpoints respond to GET requests without requiring authentication or CSRF tokens
  4. Inspect response Content-Type header
    Make a request to the JSON endpoint and examine the Content-Type response header. Vulnerable endpoints typically return 'text/javascript' or 'application/javascript' instead of 'application/json'.
    Affected if Response Content-Type is 'text/javascript' or 'application/javascript' rather than 'application/json' or includes JSON data executable as JavaScript
  5. Confirm lack of origin validation
    Check if JSON endpoints validate the Origin or Referer header, require CSRF tokens in request parameters/headers, or require POST method for sensitive JSON responses.
    Affected if No Origin/Referer validation, CSRF token requirement, or POST-only enforcement exists for JSON endpoints

Your environment is affected if Dojo Toolkit is used and JSON endpoints that leverage Dojo's data exchange are accessible via GET requests without CSRF tokens, origin validation, or proper Content-Type headers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement CSRF tokens or request origin validation (Referer/Origin header checks) for JSON endpoints, and consider using POST instead of GET for sensitive JSON responses to prevent cross-origin data theft.

Fix this in Dojo Toolkit Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2376 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-2376 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data