CVE-2023-30533
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 · uneditedSheetJS 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.
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 · high confidenceSheetJS Community Edition (a JavaScript library for reading/writing spreadsheet files) versions 0.19.2 and earlier are vulnerable to Prototype Pollution when processing a specially crafted malicious spreadsheet file. An attacker can exploit this to modify JavaScript object prototypes, potentially leading to code execution or data manipulation.
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< 0.19.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed SheetJS versionRun 'npm list sheetjs' or check package.json for the sheetjs version entryAffected if version listed is below 0.19.3 (e.g., 0.19.2, 0.18.x, etc.)
-
Identify SheetJS import in codebaseSearch source files for 'require("sheetjs")', 'import * as XLSX', or 'xlsx' package referencesAffected if the application imports or requires the SheetJS library
-
Confirm spreadsheet parsing is in useSearch for XLSX.read, XLSX.utils.sheet_to_json, or similar parsing functions in your codeAffected if the code reads or parses spreadsheet files using SheetJS
-
Determine if external files are processedReview whether user-uploaded files, API-imported spreadsheets, or files from untrusted sources are passed to SheetJS parsing functionsAffected if the application processes spreadsheet files from users or external sources without sanitization
You are affected if your installed SheetJS version is below 0.19.3 AND your application parses spreadsheet files, especially from untrusted or user-uploaded sources.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped0.19.3
Upgrade SheetJS to version 0.19.3 or later. If immediate upgrading is not feasible, implement input validation and sandboxing around file parsing operations.
0.19.3
- Check the current version of SheetJS in use (e.g., via package.json or dependency list)
- Update SheetJS to version 0.19.3 or later using your package manager (e.g., npm install [email protected] or npm install sheetjs@latest)
- Verify the installed version matches 0.19.3 or later using npm list sheetjs
- Re-test the application to confirm functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30533 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30533 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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