Is there a patch available for EUVD-2026-22192?

Yes, a patch is available for EUVD-2026-22192. Update the affected software to the latest version immediately.

Maxkb EUVD-2026-22192

Q: What is the CVSS score of EUVD-2026-22192?

EUVD-2026-22192 has a CVSS 4.0 base score of 5.1 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

| CVE-2026-39425 MEDIUM

Basic XSS (CWE-80)

2026-04-14 GitHub_M

XSS Information Disclosure Maxkb 1Panel Dev

5.1

CVSS 4.0 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

5.1 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Scope

Lifecycle Timeline

Patch released

Apr 20, 2026 - 17:31 nvd

Patch available

Apr 16, 2026 - 05:29 EUVD

2.8.0

Analysis Generated

Apr 14, 2026 - 04:10 vuln.today

CVSS changed

Apr 14, 2026 - 02:22 NVD

5.1 (MEDIUM)

EUVD ID Assigned

Apr 14, 2026 - 02:00 euvd

EUVD-2026-22192

Analysis Generated

Apr 14, 2026 - 02:00 vuln.today

CVE Published

Apr 14, 2026 - 01:18 nvd

MEDIUM 5.1

DescriptionGitHub Advisory

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 <html_rander> 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/{workspace_id}/application endpoint, storing the raw payload directly in the database. The frontend then renders this content using an innerHTML-equivalent mechanism, trusting <html_rander>-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.

AnalysisAI

Stored Cross-Site Scripting in MaxKB 2.7.1 and below allows authenticated users to inject arbitrary JavaScript into the Application prologue field via <html_rander> tags, which the backend stores unsanitized and the frontend renders with innerHTML-equivalent mechanisms. Exploitation enables session hijacking, unauthorized workspace/application deletion, and sensitive data exposure against any visitor accessing the affected chatbot. Fixed in version 2.8.0.

Technical ContextAI

MaxKB is an open-source AI assistant platform (CPE: cpe:2.3:a:1panel-dev:maxkb) that provides enterprise chatbot functionality. The vulnerability exists in the /admin/api/workspace/{workspace_id}/application endpoint, which accepts and stores the prologue (Opening Remarks) field without HTML sanitization or entity encoding. The root cause is improper input validation and output encoding (CWE-80: Improper Neutralization of Argument Delimiters in a Command). The frontend trusts <html_rander>-wrapped content as safe and renders it using innerHTML or equivalent DOM manipulation, creating a persistent stored XSS condition. When authenticated users craft payloads wrapped in <html_rander> tags, the backend stores the raw HTML/JavaScript directly in the database, and subsequent page loads execute the malicious script in the context of any visitor's browser session.

RemediationAI

Vendor-released patch: MaxKB 2.8.0. Upgrade MaxKB to version 2.8.0 or later immediately via the official GitHub releases (https://github.com/1Panel-dev/MaxKB/releases/tag/v2.8.0) or your package manager. For deployments unable to upgrade immediately, restrict API access to the /admin/api/workspace/{workspace_id}/application endpoint using network-level controls or authentication middleware to minimize the number of users who can inject payloads. Additionally, implement Content Security Policy (CSP) headers to prevent inline script execution as a temporary mitigation, though this does not replace patching. After upgrading, audit all applications created or modified in versions 2.7.1 and below for <html_rander>-wrapped payloads in the prologue field and remove or sanitize them manually if discovered.