Security Resilience

CVE-2023-30533

Sheetjs ≤ 0.19.3

Published
24 April 2023
Modified
04 February 2025
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0099 62th percentile
Risk Priority 65 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-30533 is a high-severity Prototype Pollution (CWE-1321) vulnerability in Sheetjs. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 38% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

SheetJS Community Edition before version 0.19.3 is affected by a prototype pollution vulnerability, tracked as CVE-2023-30533 and assigned CWE-1321. The flaw allows an attacker to supply a specially crafted spreadsheet file that, when parsed by the library, pollutes JavaScript object prototypes. The issue is present in all releases through 0.19.2 and was corrected in 0.19.3.

An attacker can exploit the vulnerability by delivering a malicious file to a victim who then opens it with an application that uses the vulnerable SheetJS library. Because the CVSS vector indicates local access, no privileges, and required user interaction, successful exploitation can result in arbitrary code execution or other impacts that affect confidentiality, integrity, and availability.

The vendor advisory at cdn.sheetjs.com and the project changelog both recommend upgrading to SheetJS Community Edition 0.19.3 or later. The associated Git repository issue and commit history confirm that the prototype-pollution vectors were removed in that release.

The EPSS score has remained flat at 0.0880 with no material increase since disclosure.

EU & UK References

Vulnerability Data

SheetJS Community Edition before 0.19.3 allows Prototype Pollution via a crafted file. In other words. 0.19.2 and earlier are affected, whereas 0.19.3 and later are unaffected.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-45827Shared CWE-1321
CVE-2023-2972Shared CWE-1321
CVE-2026-97151Shared CWE-1321
CVE-2024-39018Shared CWE-1321
CVE-2026-23736Shared CWE-1321
CVE-2026-48713Shared CWE-1321
CVE-2025-57325Shared CWE-1321
CVE-2025-63703Shared CWE-1321
CVE-2026-31865Shared CWE-1321
CVE-2026-32886Shared CWE-1321

Affected Assets

sheetjs
sheetjs
≤ 0.19.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches prototype-pollution flaws before release.

prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

blocks

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References