Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-39381: CWE-863: Incorrect Authorization in parse-community parse-server

0
Medium
VulnerabilityCVE-2026-39381cvecve-2026-39381cwe-863
Published: Tue Apr 07 2026 (04/07/2026, 19:51:03 UTC)
Source: CVE Database V5
Vendor/Project: parse-community
Product: parse-server

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.8.0-alpha.7 and 8.6.75, the GET /sessions/me endpoint returns _Session fields that the server operator explicitly configured as protected via the protectedFields server option. Any authenticated user can retrieve their own session's protected fields with a single request. The equivalent GET /sessions and GET /sessions/:objectId endpoints correctly strip protected fields. This vulnerability is fixed in 9.8.0-alpha.7 and 8.6.75.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/07/2026, 20:17:15 UTC

Technical Analysis

Parse Server versions >= 9.0.0 and < 9.8.0-alpha.7, as well as versions >= 7.0.0 and < 8.6.75, contain an incorrect authorization vulnerability (CWE-863) in the GET /sessions/me endpoint. This endpoint returns _Session fields configured as protected via the protectedFields server option, allowing any authenticated user to retrieve their own session's protected fields. The GET /sessions and GET /sessions/:objectId endpoints do not exhibit this behavior and correctly strip protected fields. The vulnerability is addressed in parse-server versions 9.8.0-alpha.7 and 8.6.75.

Potential Impact

Authenticated users can access protected session fields that should be restricted, potentially exposing sensitive session information. The vulnerability does not allow access to other users' sessions or escalate privileges beyond the authenticated user's own session data. The CVSS 4.0 base score is 5.3, indicating a medium severity impact.

Mitigation Recommendations

Upgrade parse-server to version 9.8.0-alpha.7 or later, or 8.6.75 or later, where this vulnerability is fixed. There is no official remediation level stated beyond the fix in these versions. Patch status is confirmed by the version fix information. No additional mitigation is indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-06T22:06:40.515Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 69d56287aaed68159a58f984

Added to database: 4/7/2026, 8:01:11 PM

Last enriched: 4/7/2026, 8:17:15 PM

Last updated: 4/8/2026, 12:43:04 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses