Skip to content

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

High severity GitHub Reviewed Published Nov 5, 2025 in parse-community/parse-server • Updated Nov 5, 2025

Package

npm parse-server (npm)

Affected versions

>= 4.2.0, < 7.5.4
>= 8.0.0, <= 8.4.0-alpha.1

Patched versions

7.5.4
8.4.0-alpha.2

Description

Impact

A Server-Side Request Forgery (SSRF) vulnerability in the file upload functionality when trying to upload a Parse.File with uri parameter allows to execute 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.

Patches

The feature has been implemented in Parse Server 4.2.0 but never worked and reliably crashes the server when trying to use it due to a bug in its implementation. Since the feature is not currently working, and due to its risky nature, it has been removed to address the vulnerability.

Workarounds

None.

References

@mtrezza mtrezza published to parse-community/parse-server Nov 5, 2025
Published to the GitHub Advisory Database Nov 5, 2025
Reviewed Nov 5, 2025
Last updated Nov 5, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Weaknesses

No CWEs

CVE ID

CVE-2025-64430

GHSA ID

GHSA-x4qj-2f4q-r4rx

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.