dbcve.org
Parse DashboardApplication · Parseplatform

CVE-2026-27609

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Parse Dashboard is a standalone dashboard for managing Parse Server apps. In versions 7.3.0-alpha.42 through 9.0.0-alpha.7, the AI Agent API endpoint (`POST /apps/:appId/agent`) lacks CSRF protection. An attacker can craft a malicious page that, when visited by an authenticated dashboard user, submits requests to the agent endpoint using the victim's session. The fix in version 9.0.0-alpha.8 adds CSRF middleware to the agent endpoint and embeds a CSRF token in the dashboard page. As a workaround, remove the `agent` configuration block from your dashboard configuration. Dashboards without an `agent` config are not affected.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Parse Dashboard versions 7.3.0-alpha.42 through 9.0.0-alpha.7 lack CSRF protection on the AI Agent API endpoint (POST /apps/:appId/agent). An attacker can trick an authenticated dashboard user into submitting requests to this endpoint by hosting a malicious page, allowing cross-site request forgery attacks using the victim's session credentials.

MitigationUpgrade Parse Dashboard to version 9.0.0-alpha.8 or later which implements CSRF middleware and token embedding. As an alternative workaround, remove the 'agent' configuration block from the dashboard configuration to disable the affected endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Parse DashboardApplication
Affected:= 7.3.0= 7.4.0= 7.5.0= 7.6.0= 8.0.0= 8.1.0= 8.1.1= 8.2.0= 8.3.0= 8.4.0= 8.4.1= 8.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Parse Dashboard version
    Run 'npm list parse-dashboard' or check package.json for the installed parse-dashboard version number
    Affected if Version is 7.3.0, 7.4.0, 7.5.0, 7.6.0, 8.0.0, 8.1.0, 8.1.1, 8.2.0, 8.3.0, 8.4.0, 8.4.1, or 8.5.0 (or any 7.3.0-alpha.42 through 9.0.0-alpha.7 build)
  2. Locate dashboard configuration file
    Find the parse-dashboard-config.json or config file used when starting Parse Dashboard (commonly in the dashboard root or /config directory)
    Affected if Configuration file exists and can be inspected
  3. Check if agent configuration block exists
    Open the configuration file and search for an 'agent' or 'AIAgent' block/section that defines the agent endpoint settings
    Affected if An 'agent' configuration block is present and enabled (not commented out or set to disabled)
  4. Verify CSRF middleware is not enforced
    Inspect the dashboard source code or middleware configuration for CSRF token validation on POST requests to /apps/*/agent routes
    Affected if No CSRF token validation is present on the /apps/:appId/agent endpoint

You are affected if Parse Dashboard version is between 7.3.0-alpha.42 and 9.0.0-alpha.7 AND the agent configuration block is present and enabled in your dashboard configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Parse Dashboard to version 9.0.0-alpha.8 or later which implements CSRF middleware and token embedding. As an alternative workaround, remove the 'agent' configuration block from the dashboard configuration to disable the affected endpoint.

Recommended fix High confidence

9.0.0-alpha.8

  1. Upgrade Parse Dashboard to version 9.0.0-alpha.8 or later to obtain the CSRF protection fix
  2. If immediate upgrade is not possible, remove the `agent` configuration block from your dashboard configuration file as a workaround
Caveat Upgrading to alpha version 9.0.0-alpha.8 may introduce other changes; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Parse Dashboard Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27609 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27609 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data