CVE-2025-57328
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 · uneditedtoggle-array is a package designed to enables a property on the object at the specified index, while disabling the property on all other objects. A Prototype Pollution vulnerability in the enable and disable function of toggle-array v1.0.1 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.
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 confidenceThe toggle-array package versions v1.0.1 and earlier contain a Prototype Pollution vulnerability in the enable and disable functions. These functions allow attackers to inject arbitrary properties into Object.prototype by using crafted payloadsinstead of valid array indices (e.g., using __proto__ or constructor as keys), enabling denial of service and potentially more severe attacks.
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<= 1.0.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Locate toggle-array in your project dependenciesSearch your package.json files and node_modules directory for the toggle-array package. Run `npm list toggle-array` or `grep -r "toggle-array" package.json` in your project root.Affected if toggle-array is listed as a direct or transitive dependency
-
Identify the installed versionRun `npm list toggle-array` or check the version field in node_modules/toggle-array/package.json. Compare this version to the affected range (v1.0.1 and earlier).Affected if The installed version is 1.0.1 or any earlier version (e.g., 1.0.0, 0.x.x)
-
Inspect code using enable or disable functionsSearch your codebase for calls to toggleArray.enable() or toggleArray.disable() methods. Review how the index/key argument is obtained (e.g., from user input, API parameters, or external data).Affected if The enable or disable functions accept index values from untrusted sources without validation
-
Verify input validation on array index parametersExamine the enable and disable function implementations in node_modules/toggle-array/index.js (or the actual source file). Check whether the code validates that the provided key is a valid array index (integer >= 0) and rejects special property names.Affected if The code does not validate that keys are valid array indices and would accept __proto__, constructor, or other prototype properties
You are affected if toggle-array version 1.0.1 or earlier is installed AND your code passes unvalidated user-controlled input to the enable or disable functions as array indices.
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.
From vendor dataUpgrade to a patched version of toggle-array (v1.0.2 or later) that implements input validation to reject prototype-injecting property names as array indices.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57328 — 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-2025-57328 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