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-27608: CWE-862: Missing Authorization in parse-community parse-dashboard

0
Critical
VulnerabilityCVE-2026-27608cvecve-2026-27608cwe-862
Published: Wed Feb 25 2026 (02/25/2026, 02:16:30 UTC)
Source: CVE Database V5
Vendor/Project: parse-community
Product: parse-dashboard

Description

CVE-2026-27608 is a critical authorization bypass vulnerability in parse-community's parse-dashboard versions 7. 3. 0-alpha. 42 through 9. 0. 0-alpha. 7. The AI Agent API endpoint (`POST /apps/:appId/agent`) fails to enforce proper authorization, allowing authenticated users scoped to one app to access and manipulate other apps' agent endpoints by altering the app ID in the URL. Read-only users are incorrectly granted the full master key and can perform unauthorized write and delete operations. This flaw affects only dashboards with the `agent` configuration enabled.

AI-Powered Analysis

AILast updated: 02/25/2026, 03:26:43 UTC

Technical Analysis

Parse Dashboard is a management interface for Parse Server applications. In versions 7.3.0-alpha.42 through 9.0.0-alpha.7, a critical vulnerability (CVE-2026-27608) exists in the AI Agent API endpoint (`POST /apps/:appId/agent`). This endpoint does not enforce proper authorization checks, allowing authenticated users with access scoped to specific apps to bypass restrictions by modifying the app ID parameter in the URL to access other apps' agent endpoints. Additionally, users with read-only roles are mistakenly provided the full master key instead of a restricted read-only master key. This misconfiguration enables them to escalate privileges by supplying write permissions in the request body, thereby performing unauthorized write and delete operations on other apps. The vulnerability only affects dashboards that have the `agent` configuration enabled; dashboards without this configuration are not impacted. The fix introduced in version 9.0.0-alpha.8 adds per-app authorization enforcement and restricts read-only users to the read-only master key with server-side stripping of write permissions. No known exploits are reported in the wild yet. The vulnerability is classified under CWE-862 (Missing Authorization). The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required beyond authenticated user, no user interaction, and high impact on confidentiality, integrity, and availability, with scope changed due to cross-app access. This vulnerability poses a severe risk of unauthorized data access and manipulation across multiple Parse Server applications managed via the dashboard.

Potential Impact

This vulnerability allows authenticated users scoped to a single app to access and manipulate data of other apps managed by the same parse-dashboard instance, violating data confidentiality and integrity. Read-only users can escalate privileges to perform write and delete operations, potentially leading to data loss, unauthorized data modification, and disruption of service availability. Organizations relying on parse-dashboard with the vulnerable versions and agent feature enabled face risks of cross-application data breaches and operational disruption. The impact is critical because it affects multiple security properties (confidentiality, integrity, availability) and can be exploited remotely without additional user interaction or elevated privileges beyond authentication. This could lead to significant reputational damage, regulatory compliance violations, and financial losses, especially for multi-tenant environments or SaaS providers using parse-dashboard for app management.

Mitigation Recommendations

1. Upgrade parse-dashboard to version 9.0.0-alpha.8 or later, which includes the fix with per-app authorization checks and proper permission restrictions for read-only users. 2. As an immediate workaround, remove the `agent` configuration block from the dashboard configuration to disable the vulnerable AI Agent API endpoint. 3. Audit and restrict user roles and permissions to minimize exposure, ensuring that users have the least privilege necessary. 4. Monitor dashboard access logs for suspicious activity, such as unexpected app ID changes in API requests or unauthorized write/delete operations. 5. Implement network segmentation and access controls to limit dashboard access to trusted users and networks. 6. Conduct security reviews of dashboard configurations regularly to ensure no unintended features like `agent` are enabled without proper controls. 7. Educate administrators about this vulnerability and the importance of timely patching and configuration management.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-20T19:43:14.602Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699e6864b7ef31ef0bae9d05

Added to database: 2/25/2026, 3:11:32 AM

Last enriched: 2/25/2026, 3:26:43 AM

Last updated: 2/25/2026, 8:13:09 AM

Views: 6

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats