CVE-2026-27609

6.5 MEDIUM

📋 TL;DR

Parse Dashboard versions 7.3.0-alpha.42 through 9.0.0-alpha.7 lack CSRF protection on the AI Agent API endpoint. This allows attackers to craft malicious pages that, when visited by authenticated dashboard users, can submit unauthorized requests to the agent endpoint using the victim's session. Only dashboards with the 'agent' configuration block enabled are affected.

💻 Affected Systems

Products:
  • Parse Dashboard
Versions: 7.3.0-alpha.42 through 9.0.0-alpha.7
Operating Systems: All
Default Config Vulnerable: ✅ No
Notes: Only dashboards with the 'agent' configuration block enabled are vulnerable. Dashboards without this configuration are not affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

An attacker could execute arbitrary AI agent operations on behalf of authenticated users, potentially manipulating AI behavior, accessing sensitive data processed by agents, or disrupting AI-powered functionality.

🟠

Likely Case

Attackers could perform unauthorized AI agent operations, potentially leading to data exposure, manipulation of AI responses, or disruption of AI-powered dashboard features.

🟢

If Mitigated

With proper CSRF protection, only legitimate dashboard sessions can access the agent endpoint, preventing unauthorized cross-origin requests.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires the victim to be authenticated to the dashboard and visit a malicious page. The attack leverages standard CSRF techniques.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 9.0.0-alpha.8 and later

Vendor Advisory: https://github.com/parse-community/parse-dashboard/security/advisories/GHSA-3534-xp88-25rc

Restart Required: Yes

Instructions:

1. Update Parse Dashboard to version 9.0.0-alpha.8 or later. 2. Restart the Parse Dashboard service. 3. Verify the fix by checking that CSRF tokens are present in dashboard requests to the agent endpoint.

🔧 Temporary Workarounds

Remove agent configuration

all

Disable the AI Agent functionality by removing the 'agent' configuration block from your dashboard configuration file.

Edit your Parse Dashboard configuration file and remove or comment out the 'agent' configuration block.

🧯 If You Can't Patch

  • Implement additional CSRF protection at the web application firewall or reverse proxy level.
  • Restrict dashboard access to trusted networks only and implement strict CORS policies.

🔍 How to Verify

Check if Vulnerable:

Check if your Parse Dashboard version is between 7.3.0-alpha.42 and 9.0.0-alpha.7 and has the 'agent' configuration enabled.

Check Version:

Check the Parse Dashboard version in your deployment configuration or run 'npm list parse-dashboard' if using npm.

Verify Fix Applied:

After updating to 9.0.0-alpha.8 or later, verify that POST requests to the agent endpoint include a valid CSRF token and that the dashboard page embeds CSRF tokens.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to /apps/*/agent endpoint without proper referrer headers or CSRF tokens
  • Multiple failed CSRF validation attempts on agent endpoint

Network Indicators:

  • Cross-origin POST requests to the agent endpoint from untrusted domains
  • Requests to agent endpoint without proper authentication headers

SIEM Query:

source="parse-dashboard" AND (url_path="/apps/*/agent" AND http_method="POST") AND (NOT csrf_token_valid="true" OR referrer NOT IN trusted_domains)

🔗 References

📤 Share & Export