Parse Javascript SDK vulnerable to prototype pollution in Parse.Object and internal APIs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L

EPSS

• CVE-2025-62374: 0.42% estimated exploitation activity in the next 30 days; percentile 36.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Prototype pollution capabilities on various APIs. Details Injection of malicious payload allows attacker to remotely execute arbitrary code. Parse.Object and internal APIs are affected, specifically: - ParseObject.fromJSON - ParseObject.pin - ParseObject.registerSubclass - ObjectStateMutations (internal) - encode/decode (internal) PoC Demonstrative tests added as part of the fix. References - https://github.com/parse-community/Parse-SDK-JS/security/advisories/GHSA-9f2h-7v79-mxw3 - Patch https://github.com/parse-community/Parse-SDK-JS/releases/tag/7.0.0-alpha.1

Published by the source

14 Oct 2025, 22:24 UTC

Last modified by the source

14 Oct 2025, 22:57 UTC

Source last checked

26 Oct 2026, 12:38 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9f2h-7v79-mxw3

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9f2h-7v79-mxw3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-62374

Advisory: Parse Javascript SDK vulnerable to prototype pollution in `Parse.Object` and internal APIs
IDs: CVE-2025-62374, GHSA-9f2h-7v79-mxw3
Record: https://patchnext.com/advisories/cve-2025-62374 (revision 2, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: parse 7.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm parse: affected < 7.0.0; fixed in 7.0.0

## Suggested inspection (read-only)
- `npm ls parse --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on parse.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9f2h-7v79-mxw3 (OSV record GHSA-9f2h-7v79-mxw3 lists affected ranges: npm parse >=0 <7.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-9f2h-7v79-mxw3 (GitHub-reviewed advisory GHSA-9f2h-7v79-mxw3 lists affected ranges: npm parse >=0 <7.0.0)

Commands are suggestions: review each one before running it.