CVE-2026-27595: 
JavaScript vulnerability analysis and mitigation

CVE-2026-27595 is a missing authentication vulnerability in the AI Agent API endpoint of Parse Dashboard, a standalone management interface for Parse Server applications. Affecting versions 7.3.0-alpha.42 through 9.0.0-alpha.7 (Node.js package), the flaw allows unauthenticated remote attackers to chain multiple security weaknesses to perform arbitrary read and write operations against any connected Parse Server database using the master key. The vulnerability was published on February 23–25, 2026, with a patch released in version 9.0.0-alpha.8. It carries a CVSS v3.1 score of 7.5 (High) and a CVSS v4.0 score of 9.9 (Critical) (GitHub Advisory, Parse Dashboard Advisory).

The root cause is CWE-306 (Missing Authentication for Critical Function): the AI Agent API endpoint POST /apps/:appId/agent was implemented without authentication middleware, CSRF validation, or per-app authorization controls. An attacker can send unauthenticated HTTP POST requests directly to this endpoint, which internally uses the Parse Server master key to execute database operations — bypassing all normal access controls. Additional compounding issues include a cache key collision between the master key and the read-only master key, which could allow privilege escalation within the dashboard's key management logic. The vulnerability is only exploitable on deployments where the agent feature has been explicitly enabled in the dashboard configuration (GitHub Advisory, Parse Dashboard Advisory).

Successful exploitation allows unauthenticated remote attackers to perform complete database compromise — reading, modifying, or deleting any data in the connected Parse Server database using master key privileges. Because the master key bypasses all Parse Server class-level permissions and ACLs, an attacker gains unrestricted access to all application data, user records, and credentials stored in the database. The impact extends to subsequent systems (CVSS v4 SC:H/SI:H), meaning downstream services or applications relying on the Parse Server database are also at risk. Deployments without the agent feature configured are not affected (GitHub Advisory).

No public proof-of-concept exploit code or evidence of in-the-wild exploitation has been reported as of the time of disclosure (GitHub Advisory). The EPSS score is approximately 0.021% (6th percentile), indicating a low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. No threat actor attribution has been identified. The vulnerability was reported by researcher ByamB4 and coordinated by mtrezza (Parse Dashboard Advisory).

1. Reconnaissance: Identify internet-facing Parse Dashboard instances (versions 7.3.0-alpha.42 through 9.0.0-alpha.7) using tools like Shodan or Censys, searching for the Parse Dashboard web interface. Confirm the target has the AI Agent feature enabled by checking for a response from the agent endpoint.
2. Identify target app ID: Browse or enumerate the Parse Dashboard to identify valid appId values, which may be visible in the dashboard URL or API responses.
3. Send unauthenticated request: Craft an HTTP POST request to POST /apps/:appId/agent without any authentication headers or session tokens, including a malicious payload in the request body targeting desired database operations.
4. Execute arbitrary database operations: The endpoint processes the request using the Parse Server master key, allowing the attacker to read sensitive data (user records, credentials, application data), write or modify records, or delete data from any class in the connected Parse Server database.
5. Exploit cache key collision (optional): Leverage the cache key collision between the master key and read-only master key to potentially escalate from read-only to full write access in certain configurations (GitHub Advisory, Parse Dashboard Advisory).

• Network: Unexpected or anomalous HTTP POST requests to /apps/<appId>/agent originating from unknown or external IP addresses, especially without session cookies or authentication headers.
• Logs: Parse Dashboard access logs showing POST requests to the /apps/:appId/agent endpoint from unauthenticated sources; unusual volume of database read/write operations correlated with agent endpoint activity.
• Database: Unexpected modifications, deletions, or bulk reads of Parse Server database records not attributable to known application activity or authenticated users; new or modified records in sensitive classes (e.g., _User, _Session).
• Application: Anomalous master key usage in Parse Server logs not initiated by legitimate dashboard sessions.

Upgrade Parse Dashboard to version 9.0.0-alpha.8 or later, which adds authentication middleware, CSRF validation, and per-app authorization controls to the agent endpoint, restricts read-only users to readOnlyMasterKey with write permissions stripped server-side, and corrects the cache key collision (Parse Dashboard Release). If immediate patching is not possible, remove or comment out the agent configuration block from the Parse Dashboard configuration file to disable the vulnerable endpoint entirely — dashboards without an agent config are not affected (GitHub Advisory). Prioritize patching any internet-facing Parse Dashboard instances with the agent feature enabled.

The vulnerability was coordinated and published by Parse Dashboard maintainer mtrezza, with the reporter credited as ByamB4 (Parse Dashboard Advisory). No significant broader media coverage or notable public researcher commentary beyond the official advisory has been identified at this time.