CVE-2026-39425: MaxKB: Stored XSS via Unsanitized html_rander Tags in Markdown Rendering
MaxKB is an open-source AI assistant for enterprise. Versions 2.7.1 and below contain a Stored Cross-Site Scripting (XSS) vulnerability that allows authenticated users to inject arbitrary HTML and JavaScript into the Application prologue (Opening Remarks) field by wrapping malicious payloads in <htmlrander> tags. The backend fails to sanitize or encode HTML entities in the prologue field when applications are created or updated via the /admin/api/workspace/{workspaceid}/application endpoint, storing the raw payload directly in the database. The frontend then renders this content using an innerHTML-equivalent mechanism, trusting <htmlrander>-wrapped content to be safe, which enables persistent DOM-based Stored XSS execution against any visitor who opens the affected chatbot interface. Exploitation can lead to session hijacking, unauthorized actions performed on behalf of victims (such as deleting workspaces or applications), and sensitive data exposure. This issue has been fixed in version 2.8.0.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39425?
CVE-2026-39425 is classified as a High severity vulnerability due to its potential for allowing attackers to execute arbitrary scripts in the context of the application.
How do I fix CVE-2026-39425?
To fix CVE-2026-39425, upgrade MaxKB to version 2.8.0 or later, which addresses the vulnerability by sanitizing the HTML inputs.
Who is affected by CVE-2026-39425?
CVE-2026-39425 affects authenticated users of MaxKB versions 2.7.1 and below.
What type of vulnerability is CVE-2026-39425?
CVE-2026-39425 is a Stored Cross-Site Scripting (XSS) vulnerability that occurs due to unsanitized html_rander tags in Markdown rendering.
Can CVE-2026-39425 be exploited remotely?
Yes, CVE-2026-39425 can be exploited remotely by authenticated users who can inject malicious scripts into the application.