# CVE-2026-85230: MISP Dashboard Button Widget Allows Persistent JavaScript URL Injection > Authenticated users can inject malicious JavaScript URLs into MISP dashboard widgets, potentially enabling script execution and session data access. - **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 3 Sep 2026 - **Updated:** 3 Sep 2026 - **Also known as:** GHSA-gp3m-78wh-q857 ## What is CVE-2026-85230? CVE-2026-85230 is a medium-severity cross-site scripting vulnerability in Misp-Project Misp, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A persistent unsafe URL injection vulnerability exists in the MISP dashboard ButtonWidget configuration. Dashboard widget URLs were validated only when the widget was rendered and were not validated when the configuration was saved. As a result, an authenticated user able to modify dashboard widget settings could persist arbitrary URL values, including URLs using the javascript: scheme, through either of the dashboard settings persistence paths. A malicious javascript: URL stored in a dashboard button could potentially result in client-side script execution in the MISP security context if the value reached a rendering or navigation path without the existing runtime validation. Such execution could allow an attacker to perform actions with the privileges of the affected user or access information available to their MISP session. The practical exploitability of this issue is reduced by the fact that MISP already applied URL validation at render time, which neutralized known malicious values before they were presented to the user. The vulnerability therefore represents a persistence-layer validation gap and a defense-in-depth weakness rather than evidence of a direct bypass of the existing rendering protection. The patch introduces a canonical url schema type and validates dashboard widget configuration before it is persisted through either settings save mechanism. ButtonWidget URLs must now be strings resolving to an absolute path on the current MISP instance or a full URL with the same origin. Values using javascript:, external origins, malformed URL forms, and non-string values are rejected at save time. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2026-85230? It affects 1 product. Products: Misp-Project Misp. ## How do I fix CVE-2026-85230? No fix has been published for CVE-2026-85230 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-85230 being exploited? There is no known exploitation of CVE-2026-85230 in the wild and no public exploit code. ## Other vulnerabilities in Misp-Project Misp - [CVE-2024-46918](https://insights.sbomify.com/CVE-2024-46918/): Missing authorization in n/a (critical 9.8) - [CVE-2024-45509](https://insights.sbomify.com/CVE-2024-45509/): Missing authorization in n/a (critical 9.8) - [CVE-2024-29858](https://insights.sbomify.com/CVE-2024-29858/): File upload in n/a (critical 9.8) - [CVE-2024-29859](https://insights.sbomify.com/CVE-2024-29859/): File upload in n/a (critical 9.8) - [CVE-2024-25674](https://insights.sbomify.com/CVE-2024-25674/): File upload in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-85230 and fix it if it is affected. What it is: CVE-2026-85230 is a medium-severity cross-site scripting vulnerability in Misp-Project Misp, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-85230 in the wild and no public exploit code. Affected product: Misp-Project Misp. No package-level version data is available, so check the vendor advisory linked from the reference page. 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-85230/ (Markdown: https://insights.sbomify.com/CVE-2026-85230/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85230 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85230 - OSV: https://osv.dev/vulnerability/CVE-2026-85230 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-85230/ Summaries are generated and may contain mistakes; the official description above is the record.