Is this vulnerability remotely exploitable?

Yes. If the affected adapters are exposed over the network and the configuration is incomplete, an attacker can remotely present a valid JWT from the same identity provider but issued to another app and be accepted as an authenticated user.

What level of access does an attacker need to exploit this?

The attacker needs the ability to obtain a valid identity token from Google, Apple, or Facebook for some application they can access. They do not need direct access to the Parse Server configuration; the exploit works if the server is misconfigured and accepts such tokens.

What is the safest general fix pattern?

Ensure that audience-related configuration (`clientId` for Google/Apple, `appIds` for Facebook) is explicitly set and that JWT verification fails closed when these values are missing or do not match. All tokens must be checked for correct audience, issuer, and other critical claims before authentication is granted.

Severity:

CRITICAL RISK

(9.8)

Improper Authentication (CWE-287) in Parse Server OAuth JWT Adapters

CVE-2026-30863

Published:

Mar 7, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Improper Authentication

CWE:

CWE-287;CWE-863

Impact:

Authentication Bypass and Account Compromise

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Authentication

CWE:

CWE-287;CWE-863

Impact:

Authentication Bypass and Account Compromise

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Improper Authentication (CWE-287) in Parse Server OAuth JWT Adapters

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal