# Parse Server Vulnerable to Server-Side Request Forgery (SSRF) in File Upload via URI Format

Advisory record · `GHSA-x4qj-2f4q-r4rx`

- **Identifiers:** `GHSA-x4qj-2f4q-r4rx` · `BIT-parse-2025-64430` · `CVE-2025-64430`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 5 Nov 2025
- **Updated:** 12 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Nov 2025, 19:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `parse-server` (npm): affected `>=4.2.0, <7.5.4 || >=8.0.0, <8.4.0-alpha.2`; fixed in `7.5.4`, `8.4.0-alpha.2`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0065, the 51st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 5 Nov 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-x4qj-2f4q-r4rx](https://github.com/advisories/GHSA-x4qj-2f4q-r4rx)
- [OSV: GHSA-x4qj-2f4q-r4rx](https://osv.dev/vulnerability/GHSA-x4qj-2f4q-r4rx)
- <https://github.com/parse-community/parse-server/security/advisories/GHSA-x4qj-2f4q-r4rx>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-64430>
- <https://github.com/parse-community/parse-server/pull/9903>
- <https://github.com/parse-community/parse-server/pull/9904>
- <https://github.com/parse-community/parse-server/commit/8bbe3efbcf4a3b66f4a8db9bfb18cd98c050db51>
- <https://github.com/parse-community/parse-server/commit/97763863b72689a29ad7a311dfb590c3e3c50585>
- <https://github.com/parse-community/parse-server>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x4qj-2f4q-r4rx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x4qj-2f4q-r4rx/>. Everything for agents: <https://agentprime.io/llms.txt>.
