CVE-2018-16459: Cross-Site Scripting in exceljs

exceljs Updated 02 Oct 2025

Summary

11/09/2018
Yes i
Moderate
6.1

CVE-2018-16459: Cross-Site Scripting in exceljs. Affects exceljs versions < 1.6.0. Fixed in 1.6.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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The exceljs package is an npm package used for creating and manipulating Excel files in JavaScript. It provides a convenient API for generating Excel files with various formatting options. However, versions of exceljs prior to 1.6.0 are vulnerable to cross-site scripting (XSS) attacks.

Vulnerability Detail

The vulnerability in exceljs stems from its failure to validate data from parsed XLSX files. This allows for the embedding of HTML tags, such as <script>, directly in the sheet cells. As a result, an attacker can inject malicious JavaScript code, which will be executed when the data from the sheet is displayed in a browser. This XSS vulnerability can lead to various security risks, including unauthorized access, data theft, and session hijacking.

How To Fix

Minimum fixed version

1.6.0

This is the first release that contains the fix.

npm install exceljs@1.6.0

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

Conclusion

The exceljs package prior to version 1.6.0 is vulnerable to cross-site scripting (XSS) attacks. It is crucial to update to version 1.6.0 or later to mitigate the risk of unauthorized access, data theft, and other malicious activities. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for exceljs →

Share this vulnerability

FAQ

This vulnerability allows an attacker to execute arbitrary JavaScript code in the context of a user's browser, potentially leading to unauthorized access, data theft, and other malicious activities.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will alert you if the exceljs package version is vulnerable.

Currently, there are no known workarounds for this vulnerability. It is recommended to update to the latest version of the exceljs package to mitigate the risk.

Yes, this vulnerability has been fixed in version 1.6.0 of the exceljs package. It is crucial to update to this version or later to ensure the security of your application.

For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.

How To Fix

Minimum fixed version

1.6.0

This is the first release that contains the fix.

npm install exceljs@1.6.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