https://feed.craftedsignal.io/tags/client-side-injection/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 07 Jul 2026 16:56:32 +0000https://feed.craftedsignal.io/briefs/2026-07-open-webui-stored-xss/Tue, 07 Jul 2026 16:56:32 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-open-webui-stored-xss/An authenticated attacker can achieve stored Cross-Site Scripting (XSS) in Open WebUI by manually modifying chat history requests to inject malicious HTML into citation document metadata, leading to session takeover or potential Remote Code Execution (RCE) on the server if an administrator is targeted.Open WebUI is vulnerable to a high-severity stored Cross-Site Scripting (XSS) vulnerability, identified as CVE-2026-26192, stemming from insecure iFrame rendering in its citation model. An authenticated attacker can exploit this by intercepting and modifying HTTP requests when saving chat history to inject malicious HTML content into document metadata, specifically by adding html: true and embedding an XSS payload. When another user, particularly an administrator, views a citation containing this weaponized document within a shared chat, the vulnerable Open WebUI frontend renders the content in an iFrame with insufficient sandboxing (allow-scripts and allow-same-origin are hardcoded), allowing the XSS payload to execute. This can lead to session hijacking, exfiltration of sensitive information, or, in the case of an administrator, potential server-side Remote Code Execution (RCE) by leveraging other known vulnerabilities. The vulnerability affects pip/open-webui versions prior to 0.7.0.

Attack Chain

1. An authenticated attacker logs into Open WebUI and initiates a new chat session.
2. The attacker attaches an arbitrary file as a "document source" to the chat.
3. While saving the chat history or message, the attacker uses an HTTP proxy tool (e.g., Burp Suite, Caido, ZAP) to intercept the outgoing save request.
4. Within the intercepted request's JSON body, the attacker locates the object corresponding to the document source within the history and messages objects.
5. The attacker modifies this object by adding html: true to its metadata and injects an XSS payload (e.g., <script>alert(document.cookie)</script>) into the document content field.
6. The attacker forwards the modified HTTP request, causing the Open WebUI server to store the malicious chat history with the embedded XSS payload.
7. The attacker shares the link to this weaponized chat with a victim user (e.g., via a phishing link).
8. When the victim accesses the shared chat and clicks on the malicious document citation, the Open WebUI frontend renders the content in an insecure iFrame, executing the attacker's JavaScript payload in the victim's browser context.

Impact

Successful exploitation of this vulnerability allows an attacker to execute arbitrary client-side JavaScript code in the context of the victim's browser session. For low-privilege users, this can lead to session takeover, allowing the attacker to read session tokens from local storage and exfiltrate them to an attacker-controlled server. If an administrator is targeted and views the malicious citation, the XSS payload can be used to bypass security controls and potentially achieve server-side Remote Code Execution (RCE) by chaining with other known vulnerabilities, as described in GHSA-w7xj-8fx7-wfch. This poses a significant risk to the integrity and confidentiality of data within the Open WebUI environment.

Recommendation

• Patch CVE-2026-26192 immediately: Upgrade all Open WebUI installations to version 0.7.0 or newer to mitigate the vulnerability.
• Implement Web Application Firewall (WAF) rules: Configure a WAF to inspect POST requests to chat history save endpoints for unusual modifications like the addition of html: true in JSON bodies, and block requests containing common XSS payload patterns in document content, though this may require product-specific WAF configuration for JSON body inspection.
• Educate users on phishing awareness: Warn users about suspicious shared chat links or messages that encourage clicking on document citations from unknown or untrusted sources.

]]>highadvisoryxssweb-applicationvulnerabilityclient-side-injectionopen-webuihttps://feed.craftedsignal.io/briefs/2026-07-geonetwork-xss/Fri, 03 Jul 2026 12:45:55 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-07-geonetwork-xss/A reflected Cross-Site Scripting (XSS) vulnerability, CVE-2026-39379, exists in GeoNetwork due to client-side template injection within error pages, allowing an attacker to craft a URL that, when visited by a victim, causes arbitrary JavaScript to execute in their browser in the context of their authenticated session.A critical reflected Cross-Site Scripting (XSS) vulnerability, tracked as CVE-2026-39379, has been identified in GeoNetwork, an open-source geospatial metadata catalog. This flaw stems from improper neutralization of user-controlled input in error pages, which are built using AngularJS. When a user requests a non-existent or unauthorized service URL, GeoNetwork reflects parts of the original request directly into the error page without adequate sanitization. Since this page is an AngularJS application, an attacker can embed client-side template expressions (e.g., {{...}}) within the malicious URL. Upon rendering in the victim's browser, these expressions are evaluated, leading to the execution of arbitrary JavaScript. This vulnerability affects GeoNetwork versions 3.0.0 through 3.12.12, 4.0.0-alpha.1 through 4.0.6, 4.2.0 through 4.2.14, and 4.4.0 through 4.4.9. GeoNetwork 3.x and 4.0.x lines are no longer maintained and will not receive patches.

Attack Chain

1. Craft Malicious URL: The attacker crafts a specific URL that targets a non-existent or unauthorized GeoNetwork service endpoint, embedding client-side template injection payloads (e.g., {{expression}}) within the path or query parameters.
2. Phishing Delivery: The attacker delivers this crafted malicious URL to a victim, typically via social engineering tactics such as phishing emails, instant messages, or compromised web pages, enticing the victim to click the link.
3. Victim Request: The victim, interacting with the lure, clicks the malicious URL, causing their web browser to send an HTTP GET request containing the embedded payload to the vulnerable GeoNetwork server.
4. Server Error Response: The GeoNetwork server processes the request for the invalid service. Due to its design, it generates an AngularJS-based error page that reflects portions of the original, unsanitized request URL back to the client.
5. Client-Side Template Evaluation: When the victim's browser receives and renders the error page, the AngularJS framework identifies the reflected attacker-controlled content as a template expression. It then evaluates this expression.
6. Arbitrary JavaScript Execution: The evaluation of the template expression results in the execution of the attacker's arbitrary JavaScript code within the context of the victim's browser.
7. Impact on Authenticated Session: The malicious JavaScript executes with the same permissions and within the same authenticated session as the victim user, potentially allowing for session hijacking, data exfiltration from GeoNetwork, or performing unauthorized actions on the victim's behalf.
8. Further Exploitation: The attacker leverages the executed JavaScript to achieve their objective, which could include redirecting the user to a fake login page for credential harvesting or initiating further attacks against the GeoNetwork instance.

Impact

Successful exploitation of CVE-2026-39379 allows an attacker to execute arbitrary JavaScript code within the victim's browser. This code runs in the context of the victim's authenticated session, enabling severe consequences such as session hijacking, unauthorized data exfiltration from the GeoNetwork instance, or performing actions on the victim's behalf, including modifying content or changing configurations if the victim is an administrator. Additionally, attackers could inject fake login forms or malicious content to harvest credentials or spread malware. GeoNetwork versions 3.x and 4.0.x are particularly at risk as they are archived and will not receive official fixes, necessitating immediate upgrades for affected organizations.

Recommendation

• Patch CVE-2026-39379 immediately by upgrading GeoNetwork to a fixed version (4.2.15 or later, or 4.4.10 or later).
• Deploy the Sigma rule "Detects CVE-2026-39379 Exploitation - GeoNetwork Reflected XSS Attempt" to your SIEM to identify attempts at client-side template injection via web server logs.

]]>highadvisoryxssweb-vulnerabilityclient-side-injectionangularjsghsawebserver