How broadly exploitable is this vulnerability?

Exploitability depends on how many users have linked third-party authentication providers and whether `allowExpiredAuthDataToken` is enabled. In environments where this option is true and provider IDs are guessable or discoverable, many accounts could be at risk.

Does an attacker need valid credentials or tokens from the third-party provider?

No. The attacker only needs knowledge of the target user's provider ID for an account that has linked a third-party provider, combined with access to the vulnerable Parse Server endpoint while `allowExpiredAuthDataToken` is true.

What is the safest general fix pattern?

Enforce strict authentication by requiring successful, up-to-date verification with the third-party provider before issuing a session token, and remove or avoid configurations that treat expired or unverifiable auth data as sufficient for login.

Severity:

CRITICAL RISK

(9.1)

Authentication Bypass via Third-Party Provider ID (CWE-287) in Parse Server

CVE-2026-33409

Published:

Mar 24, 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-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Authentication Bypass

CWE:

CWE-287

Impact:

Complete Account Takeover

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Authentication Bypass

CWE:

CWE-287

Impact:

Complete Account Takeover

Severity:

CRITICAL RISK

(9.1)

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 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Authentication Bypass via Third-Party Provider ID (CWE-287) in Parse Server

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

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare