CVE-2025-62374 json
Parse Javascript SDK vulnerable to prototype pollution in `Parse.Object` and internal APIs
published 2025-10-14 12 mo ago modified 2026-10-08 31 d ago also GHSA-9f2h-7v79-mxw3 , EUVD-2025-34458
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
Parse Javascript SDK provides access to the powerful Parse Server backend from your JavaScript app. Prior to 7.0.0, injection of malicious payload allows attacker to remotely execute arbitrary code. ParseObject.fromJSON, ParseObject.pin, ParseObject.registerSubclass, ObjectStateMutations (internal), and encode/decode (internal) are affected. This vulnerability is fixed in 7.0.0.
Patch / fix
- npm parse 7.0.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12 mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L |
| GitHub | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse | <7.0.0 |
7.0.0 |
Affected products
- parse-community Parse-SDK-JS
Classification
- Weakness
-
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes
References
-
github.com
/parse-community/Parse-SDK-JS/pull/2749
web
-
github.com
/parse-community/Parse-SDK-JS/commit/00973987f361368659c0c4dbf669f3897520b132
web
-
github.com
/parse-community/Parse-SDK-JS/security/advisories/GHSA-9f2h-7v79-mxw3
web
-
github.com
/parse-community/Parse-SDK-JS/releases/tag/7.0.0-alpha.1
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-62374
advisory
-
github.com
/parse-community/Parse-SDK-JS
package
Sources
- CVE List CVE-2025-62374
- GitHub Advisory GHSA-9f2h-7v79-mxw3
- NVD CVE-2025-62374
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.