← Back to results
Vulnerability record · public intelligence
CVE-2026-30941
HIGH

Parse Server has a NoSQL injection via token type in password reset and email verification endpoints

Published Mar 10, 2026 · Updated Oct 23, 2026 · Also known as BIT-parse-2026-30941, GHSA-vgjh-hmwf-c588

Severity · CVSSHIGH · 7.5
Known exploitationNot listed
EPSS / likelihood0.48%
QFinch risk score10 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

Parse Server has a NoSQL injection via token type in password reset and email verification endpoints

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

A NoSQL injection vulnerability allows an unauthenticated attacker to inject MongoDB query operators via the `token` field in the password reset and email verification resend endpoints. The `token` value is passed to database queries without type validation and can be used to extract password reset and email verification tokens.

Potential impact

A NoSQL injection vulnerability allows an unauthenticated attacker to inject MongoDB query operators via the token field in the password reset and email verification resend endpoints. The token value is passed to database queries without type validation and can be used to extract password reset and email verification tokens. Any Parse Server deployment using MongoDB with email verification or password reset enabled is affected. When emailVerifyTokenReuseIfValid is configured, the email verification token can be fully extracted and used to verify a user's email address without inbox access.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
MEDIUM
Confidence
10%
Aliases
BIT-parse-2026-30941, GHSA-vgjh-hmwf-c588

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Source repository ↗

Record history

Published Mar 10, 2026 · Last refreshed Oct 23, 2026