CVE-2025-30168: Parse server Parse Server Has An OAuth Vulnerability

MODERATE
Advisory Identifier: GHSA-837q-jhwx-cmpv
CVSS 6.9
CWE-287
Published
Advisory Summary

CVE-2025-30168 is a MODERATE (CVSS 6.9) parse server has an oauth vulnerability (CWE-287: Improper Authentication) affecting Parse server libraries in the npm ecosystem. The issue involves parse server has an oauth login vulnerability. Remediation is available by upgrading affected packages to version 7.5.2, 8.0.2.

CVE-2025-30168 at a Glance

CVE Identifier CVE-2025-30168
GHSA Identifier GHSA-837q-jhwx-cmpv
Severity MODERATE
CVSS v3.1 Base Score 6.9
CWE Classification CWE-287: Improper Authentication
Affected Product Parse server
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2025-30168

To remediate this vulnerability, upgrade all affected Parse server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

parse-server fixed: 7.5.2
npm install parse-server@7.5.2
parse-server fixed: 8.0.2
npm install parse-server@8.0.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls parse-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-30168, inspect your project dependencies using npm:

npm ls parse-server

Analyze the terminal output to locate any version of Parse server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.5.2), your application is affected.

Note: The npm ls parse-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Parse server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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](https://docs.parseplatform.org/parse-server/guide/#oauth-and-3rd-party-authentication) 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](https://docs.parseplatform.org/parse-server/guide/#oauth-and-3rd-party-authentication) 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

CVE-2025-30168 Affected Parse server Versions

2 component(s)
Fixed Versions:
7.5.28.0.2
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm
< 7.5.2
7.5.2
parse-server
npm
≥ 8.0.0
< 8.0.2
8.0.2

References

Frequently Asked Questions

What is CVE-2025-30168?
CVE-2025-30168 is a security vulnerability in Parse server involving Parse Server has an OAuth login vulnerability under CWE-287: Improper Authentication.
Which Parse server versions are affected?
Affected versions include releases prior to 7.5.2, 8.0.2 across affected packages: parse-server.
What version fixes CVE-2025-30168?
Upgrading to 7.5.2, 8.0.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is parse-server affected?
Yes, parse-server is affected in releases prior to 7.5.2, 8.0.2. Upgrade your dependency to 7.5.2, 8.0.2 or later.
What is the CVSS score of CVE-2025-30168?
CVE-2025-30168 has a CVSS v3.1 base score of 6.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N.
What CWE is associated with CVE-2025-30168?
CVE-2025-30168 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check npm dependencies for CVE-2025-30168?
Run the dependency tree command: 'npm ls parse-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-837q-jhwx-cmpv",
  "modified" : "2025-03-21T17:42:47Z",
  "published" : "2025-03-21T17:42:47Z",
  "aliases" : [ "CVE-2025-30168" ],
  "summary" : "Parse Server has an OAuth login vulnerability",
  "details" : "### Impact\n\nThe 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](https://docs.parseplatform.org/parse-server/guide/#oauth-and-3rd-party-authentication) for more information on which authentication providers are affected.\n\n### Patches\n\nThe 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](https://docs.parseplatform.org/parse-server/guide/#oauth-and-3rd-party-authentication) for how to migrate from insecure to secure authentication.\n\n### Workarounds\n\nNone.\n\n### References\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-837q-jhwx-cmpv\n- Parse Server documentation for 3rd party authentication providers: https://docs.parseplatform.org/parse-server/guide/#oauth-and-3rd-party-authentication\n- Bug fix in Parse Server 7: https://github.com/parse-community/parse-server/pull/9668\n- Bug fix in Parse Server 8: https://github.com/parse-community/parse-server/pull/9667",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "7.5.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "8.0.0"
      }, {
        "fixed" : "8.0.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-837q-jhwx-cmpv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-30168"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/9667"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/9668"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/commit/2ff9c71030bce3aada0a00fbceedeb7ae2c8a41e"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/commit/5ef0440c8e763854e62341acaeb6dc4ade3ba82f"
  }, {
    "type" : "WEB",
    "url" : "https://docs.parseplatform.org/parse-server/guide/#oauth-and-3rd-party-authentication"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-21T17:42:47Z",
    "nvd_published_at" : "2025-03-21T15:15:43Z"
  }
}