{"answers":{"affected":"2 open source packages ship an affected version, including parse-dashboard. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27609 in the wild and no public exploit code.","fix":"Upgrade parse-dashboard to 9.0.0-alpha.8 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-27609 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-27609 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- parse-dashboard (npm): affected from 7.3.0-alpha.42; fixed in 9.0.0-alpha.8\n- parse-dashboard (npm): affected from 7.3.0-alpha.42; fixed in 9.0.0-alpha.8\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-27609/ (Markdown: https://insights.sbomify.com/CVE-2026-27609/index.md)","id":"CVE-2026-27609","markdown":"https://insights.sbomify.com/CVE-2026-27609/index.md","name":"CVE-2026-27609","record":{"aliases":["GHSA-3534-xp88-25rc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Parse Dashboard","requires_auth":"none","summary":"An attacker can perform actions on behalf of an authenticated user via CSRF if the AI Agent feature is enabled.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"parse_dashboard","vendor":"parseplatform"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Parse Dashboard Missing CSRF Protection on Agent Endpoint","id":"CVE-2026-27609","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions","id":"CVE-2026-27610"},"packages":[{"ecosystem":"npm","fixed":["9.0.0-alpha.8"],"introduced":["7.3.0-alpha.42"],"last_affected":[],"package":"parse-dashboard","purl":null,"source":"GHSA-3534-xp88-25rc"},{"ecosystem":"npm","fixed":["9.0.0-alpha.8"],"introduced":["7.3.0-alpha.42"],"last_affected":[],"package":"parse-dashboard","purl":"pkg:npm/parse-dashboard","source":"GHSA-3534-xp88-25rc"}],"prev":{"headline":"Parse Dashboard Missing Authorization on Agent Endpoint","id":"CVE-2026-27608"},"products":["parse-dashboard"],"published":"2026-02-25","related":[{"cvss_score":9.9,"headline":"Parse Dashboard has incomplete authentication on AI Agent endpoint","id":"CVE-2026-27595","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":9.3,"headline":"Parse Dashboard Missing Authorization on Agent Endpoint","id":"CVE-2026-27608","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":7,"headline":"Parse Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions","id":"CVE-2026-27610","kev_date_added":null,"published":"2026-02-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-27","vendors":["parse-community"]},"summary":"An attacker can perform actions on behalf of an authenticated user via CSRF if the AI Agent feature is enabled.","url":"https://insights.sbomify.com/CVE-2026-27609/"}