CVE-2025-54803 — Vulnerability in js-toml — CVE Details
js-toml Prototype Pollution Vulnerability
Summary
Advisory Timeline
- First published August 4, 2025 (434 days ago).
- Last revised August 5, 2025 — 1 day after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
npm install js-toml@1.0.2
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (1)
Affects 1 ecosystem: npm (1).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| js-toml | npm | All versions | 1.0.2 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-1321Prototype PollutionMITRE
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 10.0 score means for each attack dimension.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
References
- https://github.com/sunnyadn/js-toml/security/advisories/GHSA-65fc-cr5f-v7r2WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-54803ADVISORY
- https://github.com/sunnyadn/js-toml/commit/b125910a3f094b744c9c3571360d4b9e3a472f66WEB
- https://gist.github.com/siunam321/f3dc4d21a5a932c67b6c11d0026f5afcWEB
- https://github.com/sunnyadn/js-tomlPACKAGE
Frequently Asked Questions
- What is CVE-2025-54803?
- js-toml Prototype Pollution Vulnerability This vulnerability has been assigned a severity rating of HIGH (CVSS score: 10.0/10).
- How do I check if my project is affected by CVE-2025-54803?
- CVE-2025-54803 affects js-toml. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-54803 and 200,000+ other known vulnerabilities.
Severity & Exploitability
Exploitation is straightforward and causes maximum impact. Patch immediately.
Also Known As
Related CVEs
- CVE-2026-107375HIGH
JHipster: SQL Injection in the Parameter of JHipster-Generated Reactive (WebFlux + R2DBC) Applicationssort
- CVE-2026-107384HIGH
MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries)
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies