Description

A vulnerability was determined in Anil-matcha Open-Generative-AI up to 1.0.11/2.0.0. Affected by this vulnerability is the function renderHistory of the file ImageStudio.js of the component Studio Components. This manipulation causes cross site scripting. The attack may be initiated remotely. The pull request to fix this issue awaits acceptance.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "3.5",
  "pubDate": "2026-09-13T23:16:28.520Z",
  "pubdate": "2026-09-13T23:16:28.520Z",
  "executiveSummary": "A Cross-Site Scripting (XSS) vulnerability exists within the Anil-matcha Open-Generative-AI application, specifically affecting versions up to 1.0.11 and 2.0.0. The vulnerability resides in the renderHistory function within the ImageStudio.js file of the Studio Components module. This flaw allows a remote, unauthenticated attacker to inject arbitrary client-side scripts into the application interface.\nThe successful exploitation of this vulnerability results in the execution of malicious scripts within the context of the victim's browser session. The risk implications include unauthorized access to sensitive session data, potential session hijacking, and the ability to perform actions on behalf of the user without their consent. The vulnerability is triggered via remote manipulation, requiring no specific local access. Given the nature of XSS, this can be leveraged to exfiltrate user cookies, modify DOM elements, or redirect users to malicious domains, severely compromising the integrity of the user interaction with the application.",
  "technicalDetails": "The vulnerability is a classic reflected or stored Cross-Site Scripting (XSS) flaw located in the renderHistory function within ImageStudio.js. The root cause of this vulnerability is the improper sanitization and encoding of user-supplied data that is subsequently rendered directly into the Document Object Model (DOM) of the application interface.\nIn the context of the Studio Components module, the renderHistory function is responsible for dynamically generating UI elements based on historical input data. If this function processes input that is not sanitized, an attacker can inject malicious HTML or JavaScript payloads. When the browser parses the output generated by renderHistory, it interprets the injected malicious strings as executable code rather than plain text.\nThe attack flow proceeds as follows: First, the attacker identifies the input vectors processed by the renderHistory function. Second, the attacker crafts a malicious payload containing JavaScript, such as <script>alert(document.cookie)</script>, and injects it into a parameter or data source that is subsequently displayed by the affected function. Third, when a victim accesses the affected component, the application renders the compromised data. Finally, the browser executes the injected script within the security context of the origin, granting the attacker control over the victim's session-related data or DOM interactions.\nThe vulnerability is present in versions up to 1.0.11 and 2.0.0 of Open-Generative-AI. It is remotely exploitable, meaning the attacker does not need prior authorization or authentication to submit the malicious input. The post-exploitation impact allows for extensive client-side attacks, including session token theft, unauthorized data exfiltration, or the further dissemination of malicious content to other application users. The reliance on vulnerable client-side rendering logic highlights a failure in implementing context-aware output encoding, which is essential for mitigating XSS in dynamic JavaScript-based applications."
}