OpenPanel CVE-2026-85610

Exploitation requires a valid OpenPanel account with at minimum read-level membership in any project on the target instance - no administrative or elevated role is needed. The chart formula feature must be accessible to the attacker's account, which based on the description is a standard capability for project members rather than a non-default or explicitly enabled configuration. No special OS platform, deployment topology, or feature flag is required beyond a network-reachable OpenPanel instance running a version prior to 2.3.0. The sole limiting factor is the requirement to hold a legitimate authenticated session; purely unauthenticated remote exploitation is not possible per the CVSS PR:L metric.

The CVSS 4.0 score of 8.7 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H) accurately captures the network-reachable, low-complexity nature of the exploit, which requires only read-level project membership and no user interaction. The cross-organization privilege escalation described in the CVE - where a scoped project member can affect the API process broadly - amplifies the real-world impact beyond what the vulnerable-system metrics alone suggest. No EPSS score was supplied in the input data, so quantitative exploitation probability cannot be stated. The CVE is not in CISA KEV, and no public proof-of-concept code has been identified at time of analysis; however, the mathjs sandbox-escape technique via matrix object prototype traversal is a well-documented research area, meaning an attacker with mathjs internals knowledge could independently reproduce it without a public PoC. Any multi-tenant OpenPanel deployment exposing chart formula features to untrusted project members - even a modest shared analytics instance - should treat patching to 2.3.0 as urgent given the low bar for exploitation once a valid account is held.

An attacker holding a read-level project membership in OpenPanel submits a crafted chart formula that navigates the mathjs matrix object prototype chain to extract the JavaScript Function constructor. The attacker then uses the constructor to invoke require('child_process') and execute a reverse shell command, establishing OS-level access under the API process account. Because the API process holds broader privileges than the project scope, the attacker can then access configuration data, credentials, and analytics data belonging to other organizations on the same instance.