CVE-2019-13506: Cross-Site Scripting in @nuxt/devalue

@nuxt/devalue Updated 02 Oct 2025

Summary

16/07/2019
Yes i
Moderate
6.1

CVE-2019-13506: Cross-Site Scripting in @nuxt/devalue. Affects @nuxt/devalue versions < 1.2.3. Fixed in 1.2.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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @nuxt/devalue package is an npm package used in web development with the Nuxt.js framework. It provides a utility for serializing and deserializing JavaScript objects. This package is vulnerable to a Cross-Site Scripting (XSS) attack due to insufficient input sanitization. Attackers can inject arbitrary JavaScript code through object keys, potentially leading to unauthorized access or manipulation of user data.

Vulnerability Detail

The vulnerability in @nuxt/devalue versions prior to 1.2.3 allows attackers to execute arbitrary JavaScript code on the client-side. This can be achieved by injecting malicious code through object keys. The lack of proper input sanitization makes it possible for an attacker to manipulate the application's behavior and potentially steal sensitive information or perform unauthorized actions on behalf of the user. The vulnerability has a CVSS score of 6.1, indicating a moderate severity level.

How To Fix

Latest published version: 2.0.2 as of 22 Oct 2026

npm install @nuxt/devalue@2.0.2

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.2.3

This is the first release that contains the fix.

npm install @nuxt/devalue@1.2.3

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

Workaround

There is no known workaround for this vulnerability. It is essential to update to the fixed version of the @nuxt/devalue package to mitigate the risk of XSS attacks.

Conclusion

The @nuxt/devalue package prior to version 1.2.3 is vulnerable to Cross-Site Scripting (XSS) attacks. It is crucial to upgrade to the fixed version to mitigate the risk of unauthorized access or manipulation of user data. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @nuxt/devalue →

Share this vulnerability

FAQ

@nuxt/devalue is an npm package used in web development with the Nuxt.js framework. It provides a utility for serializing and deserializing JavaScript objects.

Cross-Site Scripting (XSS) is a type of security vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users. This can lead to unauthorized access, data theft, or manipulation of user data.

The vulnerability in @nuxt/devalue allows attackers to execute arbitrary JavaScript code on the client-side. This can lead to unauthorized access or manipulation of user data, potentially compromising the security and integrity of your application.

Yes, upgrading to version 1.2.3 or later of the @nuxt/devalue package fixes this vulnerability. It is recommended to update your dependencies to the latest version to ensure the security of your application.

You can use Vulert's playground at Vulert 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.

How To Fix

Latest published version: 2.0.2 as of 22 Oct 2026

npm install @nuxt/devalue@2.0.2

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.2.3

This is the first release that contains the fix.

npm install @nuxt/devalue@1.2.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