Skip to content
Fencer Vulns
high 7.5

CVE-2025-64430 json

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

published 2025-11-05 12 mo ago modified 2026-06-17 4 mo ago also BIT-parse-2025-64430 , EUVD-2025-37936 , GHSA-x4qj-2f4q-r4rx

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions 4.2.0 through 7.5.3, and 8.0.0 through 8.3.1-alpha.1, there is a Server-Side Request Forgery (SSRF) vulnerability in the file upload functionality when trying to upload a Parse.File with uri parameter, allowing execution of an arbitrary URI. The vulnerability stems from a file upload feature in which Parse Server retrieves the file data from a URI that is provided in the request. A request to the provided URI is executed, but the response is not stored in Parse Server's file storage as the server crashes upon receiving the response. This issue is fixed in versions 7.5.4 and 8.4.0-alpha.1.

Patch / fix

  • npm parse-server 7.5.4, 8.4.0-alpha.2
  • bitnami parse 7.5.4, 8.4.0
  • parseplatform parse-server 7.5.4
  • parseplatform parse_server 7.5.4

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
12 mo ago

Exploit prediction

0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
npm parse-server
>=4.2.0, <7.5.4
>=8.0.0, <8.4.0-alpha.2
7.5.4
8.4.0-alpha.2
bitnami parse
>=4.2.0, <7.5.4
>=8.0.0, <8.4.0
7.5.4
8.4.0

Affected products

  • parse-community parse-server

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.