# CVE-2026-27609: Parse Dashboard Missing CSRF Protection on Agent Endpoint

> An attacker can perform actions on behalf of an authenticated user via CSRF if the AI Agent feature is enabled.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-3534-xp88-25rc

## What is CVE-2026-27609?

CVE-2026-27609 is a high-severity vulnerability in parse-community parse-dashboard, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-27609?

2 open source packages ship an affected version, including parse-dashboard. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `parse-dashboard` | npm | From 7.3.0-alpha.42 | 9.0.0-alpha.8 |
| `parse-dashboard` | npm | From 7.3.0-alpha.42 | 9.0.0-alpha.8 |

Products: Parseplatform Parse Dashboard.

## How do I fix CVE-2026-27609?

Upgrade parse-dashboard to 9.0.0-alpha.8 or later.

## Is CVE-2026-27609 being exploited?

There is no known exploitation of CVE-2026-27609 in the wild and no public exploit code.

## Other vulnerabilities in parse-community parse-dashboard

- [CVE-2026-27595](https://insights.sbomify.com/CVE-2026-27595/): Parse Dashboard has incomplete authentication on AI Agent endpoint (critical 9.9)
- [CVE-2026-27608](https://insights.sbomify.com/CVE-2026-27608/): Parse Dashboard Missing Authorization on Agent Endpoint (critical 9.3)
- [CVE-2026-27610](https://insights.sbomify.com/CVE-2026-27610/): Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27609 and fix it if it is affected.

What it is: CVE-2026-27609 is a high-severity vulnerability in parse-community parse-dashboard, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-27609 in the wild and no public exploit code.

Affected packages and fixed versions:
- parse-dashboard (npm): affected from 7.3.0-alpha.42; fixed in 9.0.0-alpha.8
- parse-dashboard (npm): affected from 7.3.0-alpha.42; fixed in 9.0.0-alpha.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27609/ (Markdown: https://insights.sbomify.com/CVE-2026-27609/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27609
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27609
- OSV: https://osv.dev/vulnerability/CVE-2026-27609

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27609/
Summaries are generated and may contain mistakes; the official description above is the record.