Parse DashboardApplication · Parseplatform

CVE-2026-27595

HIGH · 7.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 →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

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`) has multiple security vulnerabilities that, when chained, allow unauthenticated remote attackers to perform arbitrary read and write operations against any connected Parse Server database using the master key. The agent feature is opt-in; dashboards without an agent config are not affected. The fix in version 9.0.0-alpha.8 adds authentication, CSRF validation, and per-app authorization middleware to the agent endpoint. Read-only users are restricted to the `readOnlyMasterKey` with write permissions stripped server-side. A cache key collision between master key and read-only master key was also corrected. As a workaround, remove or comment out the agent configuration block from your Parse Dashboard configuration.

Technical summary

dbcve analysis · high confidence

The Parse Dashboard AI Agent API endpoint (POST /apps/:appId/agent) in versions 7.3.0-alpha.42 through 9.0.0-alpha.7 lacks authentication, CSRF validation, and per-app authorization controls, allowing unauthenticated remote attackers to execute arbitrary read and write operations on connected Parse Server databases using the master key. Additionally, a cache key collision between master key and read-only master key enabled privilege escalation.

MitigationUpgrade to Parse Dashboard version 9.0.0-alpha.8 or later which adds proper authentication, CSRF validation, and per-app authorization middleware; alternatively, remove or comment out the agent configuration block from the Parse Dashboard configuration as a workaround.

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

Affected products & versions

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

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

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

Am I affected?

dbcve checks

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

Identify Parse Dashboard version

Run `npm list parse-dashboard` or check the package.json file for the installed parse-dashboard version number

Affected if The installed version matches 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 falls between 7.3.0-alpha.42 and 9.0.0-alpha.7
Locate Parse Dashboard configuration file

Find the parse-dashboard-config.json or dashboard configuration file used in your deployment

Affected if The configuration file contains an 'agent' or 'apps' block with AI Agent settings defined
Check if AI Agent endpoint is exposed

Send a POST request to /apps/{appId}/agent without providing authentication headers or cookies

Affected if The endpoint returns a successful response (200 OK) instead of rejecting the request with 401 Unauthorized or 403 Forbidden
Test for CSRF protection on the agent endpoint

Send a POST request to /apps/{appId}/agent without the X-Parse-Dashboard-CSRF-Token header or without a valid session cookie

Affected if The request succeeds without CSRF token validation, indicating the endpoint lacks CSRF protection
Verify per-app authorization enforcement

Attempt to call the agent API using credentials from one appId on a different app's endpoint

Affected if The request succeeds, allowing cross-app access without proper authorization checks

You are affected if your Parse Dashboard version is between 7.3.0-alpha.42 and 9.0.0-alpha.7 (including the specific 7.x and 8.x releases listed) AND the AI Agent feature is configured and the /apps/:appId/agent endpoint is exposed without authentication enforcement.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade to Parse Dashboard version 9.0.0-alpha.8 or later which adds proper authentication, CSRF validation, and per-app authorization middleware; alternatively, remove or comment out the agent configuration block from the Parse Dashboard configuration as a workaround.

Recommended fix High confidence

9.0.0-alpha.8 or later stable release

1. Backup your current Parse Dashboard configuration file (usually parse-dashboard-config.json)
2. Identify if the agent configuration block is present in your configuration file
3. If upgrading, ensure your application can tolerate potential changes in version 9.0.0-alpha.8 or later
4. Stop the Parse Dashboard service
5. Upgrade Parse Dashboard to version 9.0.0-alpha.8 or later (e.g., npm install [email protected])
6. Verify the upgrade completed successfully
7. Restart Parse Dashboard service
8. Test that the dashboard loads and authenticates correctly

Caveat Alpha releases may have stability risks; review the changelog between your current version and 9.0.0-alpha.8 for any breaking changes to the dashboard API or configuration format

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

Fix this in Parse Dashboard Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-27595 — 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

Primary sources

github.comVendor Advisory
github.comRelease Notes
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-27595?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Parse Dashboard

Remediation

A high-priority fix

Fix this in Parse Dashboard 7 hrs · Moderate

Typical engagement from $1,240

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-27595 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References