CVE-2026-30962: Parse Server has a protected fields bypass via logical query operators

Published Mar 10, 2026
·
Updated

Impact

The validation for protected fields only checks top-level query keys. By wrapping a query constraint on a protected field inside a logical operator, the check is bypassed entirely. This allows any authenticated user to query on protected fields to extract field values.

All Parse Server deployments have default protected fields and are vulnerable.

Patches

The fix adds recursive validation of sub-queries with logical operators, consistent with the existing recursive validation patterns.

Workarounds

Use a beforeFind trigger on affected classes to manually inspect the query for protected field references in logical operator sub-queries and reject the request.

References

- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-72hp-qff8-4pvv - Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.6 - Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.19

Other sources

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.6 and 8.6.19, the validation for protected fields only checks top-level query keys. By wrapping a query constraint on a protected field inside a logical operator, the check is bypassed entirely. This allows any authenticated user to query on protected fields to extract field values. All Parse Server deployments have default protected fields and are vulnerable. This vulnerability is fixed in 9.5.2-alpha.6 and 8.6.19.

MITRE

Affected Software

11 affected componentsFixes available
npm/parse-server<9.5.2-alpha.6
npm/parse-server<8.6.19
npm/parse-server<8.6.19
8.6.19
npm/parse-server>=9.0.0<9.5.2-alpha.6
9.5.2-alpha.6
parseplatform Parse-server Node.js<8.6.19
parseplatform Parse-server Node.js>=9.0.0<9.5.2
parseplatform Parse-server Node.js=9.5.2-alpha1
parseplatform Parse-server Node.js=9.5.2-alpha2
parseplatform Parse-server Node.js=9.5.2-alpha3
parseplatform Parse-server Node.js=9.5.2-alpha4
parseplatform Parse-server Node.js=9.5.2-alpha5

Event History

Mar 10, 2026
CVE Published
via MITRE·08:42 PM
Data Sourced
via MITRE·08:42 PM
DescriptionWeakness
Data Sourced
via NVD·09:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 11, 2026
Advisory Published
via GitHub·12:19 AM
Data Sourced
via GitHub·12:19 AM
DescriptionWeaknessAffected Software
May 6, 58175
Event
via FIRST·07:28 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-30962?

CVE-2026-30962 is considered high severity due to the potential for authenticated users to bypass protected field restrictions.

2

How do I fix CVE-2026-30962?

To fix CVE-2026-30962, upgrade your Parse Server to version 8.6.19 or 9.5.2-alpha.6 or later.

3

What type of vulnerability is CVE-2026-30962?

CVE-2026-30962 is a logic bypass vulnerability affecting the validation of protected fields in Parse Server.

4

Who is affected by CVE-2026-30962?

All users of Parse Server versions prior to 8.6.19 and between 9.0.0 and 9.5.2-alpha.6 are affected by CVE-2026-30962.

5

Can CVE-2026-30962 be exploited by unauthenticated users?

No, CVE-2026-30962 requires authentication, allowing only authenticated users to potentially exploit the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203