Loading story…
OpenReplay fixed a critical stored cross-site scripting flaw, tracked as CVE-2026-55879, that affects versions 1.24.0 before 1.25.0 and can let an unauthenticated attacker take over dashboard accounts. The issue allows anyone with a public project key to submit malicious custom event names or page URLs that are stored by the platform and later rendered in the authenticated dashboard, where attacker-controlled JavaScript can execute in the dashboard origin, steal the session JWT from localStorage, and hijack user access. The vulnerability is rated CVSS 9.3 and mapped to CWE-79.
The remediation shipped in OpenReplay v1.25.0 and was reflected in subsequent code changes that centralized output encoding for event read paths. The patch escapes event entries and nested property maps on the backend before returning data from SearchEvents and GetEventByID, and also hardens the frontend by escaping JSON shown in EventDetailsModal, replacing innerHTML with textContent in a text measurement helper, and adding a reusable HTML-escaping utility. Together, the changes indicate the flaw stemmed from unsanitized event content being inserted into the UI without proper output encoding.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-55879 was published describing a critical unauthenticated stored XSS in OpenReplay versions 1.24.0 before 1.25.0. The advisory says attackers with a public project key could inject malicious event names or page URLs that execute in the dashboard and enable account takeover.
A GitHub commit added backend sanitization and frontend escaping changes to event data handling, including escaping strings before rendering and replacing unsafe HTML insertion patterns. The changes are consistent with remediation of a stored XSS risk in event content displayed in the dashboard.
OpenReplay published release v1.25.0, which explicitly mentions security enhancements alongside other feature additions and bug fixes. The CVE reference states this version contains the fix for the stored XSS issue affecting earlier versions.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A critical stored cross-site scripting flaw in the open-source conference management platform **pretalx** exposed conference call-for-papers systems to organizer-session compromise. Tracked as **`CVE-2026-41241`** and rated **CVSS 8.7**, the bug allowed low-privileged attackers to place malicious HTML or JavaScript in searchable fields including submission titles, speaker display names, usernames, and email addresses. When an organizer searched for the tainted record, the payload could execute in that organizer’s browser, enabling theft of visible data, access to CSRF tokens, and authenticated actions that effectively granted organizer-level control. Researcher **Elad Meged** of Novee reported the issue after validating the vulnerable workflow across roughly 40 conferences without deploying live exploit payloads against real targets, while exploit testing was kept to controlled local environments. The report said attackers could also chain the bug with a Content Security Policy bypass by uploading a JavaScript payload disguised as presentation material, and described a no-JavaScript variant that could demote administrators via a superuser-demotion endpoint triggered from an embedded image tag. Pretalx developer Tobias Kunze said 11 findings were reported on April 14, with one deemed serious, and the project fixed the vulnerability in **`v2026.1.0`**; researchers also warned that agentic AI could help identify exposed pretalx instances and scale validation or exploitation.
Jun 29, 2026
Multiple high-severity vulnerabilities in **Open WebUI** allow attackers to plant malicious chat content that executes when viewed, leading to theft of JWTs and session tokens from `localStorage`, full account takeover, and compromise of sensitive AI assets. The flaws affect markdown rendering, citation and response iframe handling, and HTML file-serving paths, including cases where attacker-controlled content was rendered with dangerous HTML processing or iframe sandbox settings such as `allow-scripts allow-forms allow-same-origin`. Reported impacts include exposure of DOM data, `indexedDB`, cookies, backend API keys, model parameter files, private databases, and other enterprise AI resources. Several reports warn that if an administrator opens a malicious shared transcript or chat, the attack can escalate from stored XSS to **remote code execution** through Open WebUI's administrative features and Python-based functions or plugins, potentially yielding code execution on the Docker container or local host. The issues were addressed across releases including **v0.6.6** and **v0.7.0** by tightening file ownership checks, removing or making optional same-origin iframe access, and recommending stronger HTML sanitization and restrictive CSP settings; one report also provided a database query to hunt for stored chats containing suspicious `data:text/html` or `javascript:` embed payloads.
Jul 7, 2026
Security researchers disclosed two high-severity vulnerabilities in the open-source **OpenCode** AI coding agent that can allow **arbitrary command execution on a developer workstation** in drive-by scenarios. **CVE-2026-22812** stems from OpenCode automatically starting an **unauthenticated HTTP server** with **permissive CORS** (`Access-Control-Allow-Origin: *`), enabling any local process—or a malicious website via cross-origin requests—to invoke sensitive local API endpoints and execute shell commands with the user’s privileges. Separately, **CVE-2026-22813** is a **critical** issue in the OpenCode web UI where the markdown renderer can inject arbitrary HTML into the DOM without sanitization (no *DOMPurify* and no CSP), enabling JavaScript execution on the `http://localhost:4096` origin and subsequent access to local APIs that can spawn processes. Mitigations are available for both OpenCode issues: **CVE-2026-22812** is fixed in **OpenCode 1.0.216**, and **CVE-2026-22813** is fixed in **OpenCode 1.1.10**. Other items in the set describe unrelated vulnerabilities in different products (e.g., a command-injection flaw in an end-of-life VS Code extension, unsafe deserialization in *LlamaIndex*, ReDoS in *LangChain*, and various web app SQLi/XSS/access-control issues) and do not materially change the OpenCode risk picture; they should be tracked separately by affected-asset ownership and exposure.
Jun 29, 2026