# CVE-2025-57324: parse is vulnerable to prototype pollution

> Attackers can cause denial of service via prototype pollution in the Parse JavaScript SDK by injecting properties into Object.prototype.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2025
- **Updated:** 25 Sep 2025
- **Also known as:** GHSA-9g8m-v378-pcg3

## What is CVE-2025-57324?

CVE-2025-57324 is a medium-severity vulnerability in n/a, published on 24 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

parse is a package designed to parse JavaScript SDK. A Prototype Pollution vulnerability in the SingleInstanceStateController.initializeState function of parse version 5.3.0 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2025-57324?

2 open source packages ship an affected version, including parse. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `parse` | npm | All versions | 7.0.0-alpha.1 |
| `parse` | npm | All versions | 7.0.0-alpha.1 |

Products: Parseplatform Parse Javascript Sdk.

## How do I fix CVE-2025-57324?

Upgrade parse to 7.0.0-alpha.1 or later.

## Is CVE-2025-57324 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57324 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57324 and fix it if it is affected.

What it is: CVE-2025-57324 is a medium-severity vulnerability in n/a, published on 24 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57324 exists.

Affected packages and fixed versions:
- parse (npm): affected all versions; fixed in 7.0.0-alpha.1
- parse (npm): affected all versions; fixed in 7.0.0-alpha.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-57324/ (Markdown: https://insights.sbomify.com/CVE-2025-57324/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-57324
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-57324
- OSV: https://osv.dev/vulnerability/CVE-2025-57324

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-57324/
Summaries are generated and may contain mistakes; the official description above is the record.