CVE-2025-52662

6.9 MEDIUM

📋 TL;DR

This vulnerability in Nuxt DevTools allows cross-site scripting (XSS) attacks that could extract authentication tokens under certain configurations. It affects Nuxt applications using vulnerable versions of Nuxt DevTools. All users of affected versions should upgrade immediately.

💻 Affected Systems

Products:
  • Nuxt DevTools
Versions: Versions before 2.6.4
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects applications with Nuxt DevTools enabled and accessible. The vulnerability requires specific configurations to be exploitable.

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal authentication tokens and hijack user sessions, potentially gaining unauthorized access to sensitive application data and functionality.

🟠

Likely Case

Attackers could execute malicious JavaScript in the context of the Nuxt DevTools interface, potentially stealing session tokens or performing actions on behalf of authenticated users.

🟢

If Mitigated

With proper content security policies and input validation, the impact would be limited to the DevTools interface itself without affecting the main application.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires the attacker to inject malicious scripts into the DevTools interface, which may require specific conditions or user interaction.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.6.4

Vendor Advisory: https://vercel.com/changelog/cve-2025-52662-xss-on-nuxt-devtools

Restart Required: Yes

Instructions:

1. Update Nuxt DevTools to version 2.6.4 or later using npm or yarn. 2. Restart your Nuxt development server. 3. Verify the update was successful.

🔧 Temporary Workarounds

Disable Nuxt DevTools

all

Temporarily disable Nuxt DevTools in development environments until patching is possible.

npm remove @nuxt/devtools
yarn remove @nuxt/devtools

Restrict DevTools Access

all

Configure firewall rules to restrict access to the DevTools interface to trusted IP addresses only.

🧯 If You Can't Patch

  • Implement strict Content Security Policy (CSP) headers to prevent script execution
  • Disable or restrict access to Nuxt DevTools interface in production environments

🔍 How to Verify

Check if Vulnerable:

Check your package.json or run 'npm list @nuxt/devtools' to see the installed version. If version is below 2.6.4, you are vulnerable.

Check Version:

npm list @nuxt/devtools | grep @nuxt/devtools

Verify Fix Applied:

After updating, verify the version is 2.6.4 or higher using 'npm list @nuxt/devtools' or check package.json.

📡 Detection & Monitoring

Log Indicators:

  • Unusual JavaScript execution in DevTools interface
  • Suspicious requests to DevTools endpoints

Network Indicators:

  • Malicious script injection attempts in DevTools traffic
  • Unexpected token extraction patterns

SIEM Query:

source="nuxt-devtools" AND (event="script_injection" OR event="token_access")

🔗 References

📤 Share & Export