Parse Server has an OAuth login vulnerability

MEDIUM 6.9CVE-2025-30168 · BIT-parse-2025-30168 · GHSA-837q-jhwx-cmpv · Published 21/03/2025 · updated 17/06/2026

In short

CVE-2025-30168 is a MEDIUM (CVSS 6.9) vulnerability affecting parse-server.
Chance of exploitation in the next 30 days (EPSS): 0.41%, higher than 34.9% of all vulnerabilities.
Fix: update to 8.0.2, 7.5.2 or later.

Package	Affected versions	Patched versions
parse-server npm	`≥ 8.0.0, < 8.0.2< 7.5.2`	`8.0.27.5.2`

Description

Impact

The 3rd party authentication handling of Parse Server allows the authentication credentials of some specific authentication providers to be used across multiple Parse Server apps. For example, if a user signed up using the same authentication provider in two unrelated Parse Server apps, the credentials stored by one app can be used to authenticate the same user in the other app. Note that this only affects Parse Server apps that specifically use an affected 3rd party authentication provider for user authentication, for example by setting the Parse Server option auth to configure a Parse Server authentication adapter. See the 3rd party authentication docs for more information on which authentication providers are affected.

Patches

The fix of this vulnerability requires to upgrade Parse Server to a version that includes the bug fix, as well as upgrade the client app to send a secure payload, which is different from the previous insecure payload. To accommodate a gradual rollout of the client app update, affected Parse Server authentication adapters now offer an enableInsecureAuth option to accept both insecure and secure payloads from clients apps. See the 3rd party authentication docs for how to migrate from insecure to secure authentication.

Workarounds

None.

References

GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-837q-jhwx-cmpv
Parse Server documentation for 3rd party authentication providers: https://docs.parseplatform.org/parse-server/guide/#oauth-and-3rd-party-authentication
Bug fix in Parse Server 7: https://github.com/parse-community/parse-server/pull/9668
Bug fix in Parse Server 8: https://github.com/parse-community/parse-server/pull/9667

NVD description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 7.5.2 and 8.0.2, the 3rd party authentication handling of Parse Server allows the authentication credentials of some specific authentication providers to be used across multiple Parse Server apps. For example, if a user signed up using the same authentication provider in two unrelated Parse Server apps, the credentials stored by one app can be used to authenticate the same user in the other app. Note that this only affects Parse Server apps that specifically use an affected 3rd party authentication provider for user authentication, for example by setting the Parse Server option auth to configure a Parse Server authentication adapter. The fix of this vulnerability requires to upgrade Parse Server to a version that includes the bug fix, as well as upgrade the client app to send a secure payload, which is different from the previous insecure payload. This vulnerability is fixed in 7.5.2 and 8.0.2.