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-33527: CWE-863: Incorrect Authorization in parse-community parse-server

0
Medium
VulnerabilityCVE-2026-33527cvecve-2026-33527cwe-863
Published: Tue Mar 24 2026 (03/24/2026, 18:22:44 UTC)
Source: CVE Database V5
Vendor/Project: parse-community
Product: parse-server

Description

CVE-2026-33527 is a medium severity vulnerability in parse-community's parse-server that allows an authenticated user to overwrite server-generated session fields such as expiresAt and createdWith via the REST API. This flaw enables bypassing the server's session lifetime policies, effectively creating permanent sessions. The vulnerability affects parse-server versions prior to 8. 6. 57 and versions from 9. 0. 0 up to but not including 9. 6. 0-alpha. 48.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/31/2026, 20:32:12 UTC

Technical Analysis

CVE-2026-33527 is an authorization bypass vulnerability classified under CWE-863 found in parse-community's parse-server, an open-source backend platform for Node.js environments. The vulnerability arises because authenticated users can manipulate server-generated session fields, specifically 'expiresAt' and 'createdWith', when updating their own session via the REST API. Normally, these fields are controlled exclusively by the server to enforce session expiration and track session origination. By overwriting these fields, an attacker can circumvent the configured session lifetime policies, resulting in sessions that do not expire as intended, effectively granting indefinite access. This flaw affects parse-server versions earlier than 8.6.57 and versions from 9.0.0 up to 9.6.0-alpha.48. The vulnerability does not require elevated privileges beyond authentication, nor does it require user interaction, making it relatively straightforward for authenticated users to exploit. The CVSS 4.0 base score is 5.3 (medium severity), reflecting the moderate impact on session integrity and availability. The issue has been addressed in versions 8.6.57 and 9.6.0-alpha.48 by restricting user ability to modify these sensitive session fields. No public exploits have been reported to date, but the vulnerability poses a risk of persistent unauthorized access if exploited.

Potential Impact

The primary impact of this vulnerability is the potential for authenticated users to maintain indefinite sessions by bypassing session expiration controls. This undermines session management security, increasing the risk of unauthorized long-term access to user accounts or services. Organizations relying on parse-server for backend services may face increased risk of account compromise, data leakage, or abuse of privileges due to persistent sessions. The vulnerability could facilitate lateral movement or privilege escalation if session persistence is leveraged in multi-user environments. Additionally, it complicates incident response and session revocation efforts, as compromised sessions may remain valid indefinitely. While exploitation requires authentication, the ease of bypassing session expiration can significantly weaken overall security posture, especially in environments with many users or where session revocation is critical. The lack of known exploits reduces immediate risk but does not eliminate the potential for future attacks.

Mitigation Recommendations

Organizations should upgrade parse-server to version 8.6.57 or later, or 9.6.0-alpha.48 or later, where the vulnerability is patched. Until upgrading, implement strict monitoring of session activity and anomalous session durations to detect potential abuse. Restrict access to the REST API to trusted users and enforce strong authentication mechanisms to reduce the risk of unauthorized session manipulation. Consider implementing additional server-side validation to reject updates to sensitive session fields from clients. Employ session management best practices such as short session lifetimes, regular session invalidation, and multi-factor authentication to mitigate the impact of persistent sessions. Review and audit session handling code and API permissions to ensure no other fields can be manipulated improperly. Finally, maintain an incident response plan that includes procedures for revoking sessions and responding to suspected session abuse.

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-03-20T18:05:11.830Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69c2d884f4197a8e3b5f966e

Added to database: 3/24/2026, 6:31:32 PM

Last enriched: 3/31/2026, 8:32:12 PM

Last updated: 5/8/2026, 3:36:02 AM

Views: 45

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