What is the CVSS score of EUVD-2026-26394?

EUVD-2026-26394 has a CVSS 3.1 base score of 6.1 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

JeeSite EUVD-2026-26394

| CVE-2026-36761 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-04-30 mitre

XSS N A

6.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.1 MEDIUM

AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Apr 30, 2026 - 20:30 vuln.today

CVSS changed

Apr 30, 2026 - 18:22 NVD

6.1 (MEDIUM)

EUVD ID Assigned

Apr 30, 2026 - 18:00 euvd

EUVD-2026-26394

Analysis Generated

Apr 30, 2026 - 18:00 vuln.today

CVE Published

Apr 30, 2026 - 00:00 nvd

MEDIUM 6.1

DescriptionCVE.org

A stored cross-site scripting (XSS) vulnerability in the /msg/msgInner/save endpoint of JeeSite v5.15.1 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted input into the msgContent parameter.

AnalysisAI

Stored cross-site scripting (XSS) in JeeSite v5.15.1 allows unauthenticated remote attackers to inject arbitrary web scripts or HTML via the msgContent parameter in the /msg/msgInner/save endpoint, affecting any user who views a message containing the malicious payload. The vulnerability requires user interaction (viewing the crafted message) but can impact confidentiality and integrity of user sessions through script execution in the victim's browser context. No public exploit code or active exploitation has been confirmed at this time.

Technical ContextAI

This is a stored XSS vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation) in JeeSite, a Java-based enterprise content management framework. The vulnerability exists in the message handling module at the /msg/msgInner/save endpoint, which fails to properly sanitize or encode user-supplied input in the msgContent parameter before storing it in a backend data store. When the stored message is later retrieved and rendered in a browser context without adequate output encoding, the malicious script executes with the privileges of the viewing user. Unlike reflected XSS, the payload persists in the application's database, making it a higher-severity class of XSS that affects all subsequent users accessing the compromised message.

RemediationAI

Upgrade JeeSite to a patched version released after v5.15.1 that includes input sanitization and output encoding fixes for the msgContent parameter in the /msg/msgInner/save endpoint. Check the official JeeSite GitHub repository (https://github.com/thinkgem/jeesite) and EUVD advisory (EUVD-2026-26394) for the specific patched version number. If immediate patching is not possible, implement compensating controls: disable or restrict access to the message save endpoint to authenticated users only (modify AV vector); enforce strict Content Security Policy (CSP) headers to prevent inline script execution even if XSS payloads are stored; sanitize all message content on output using a library like OWASP AntiSamy or DOMPurify before rendering in the browser; and conduct data cleanup by identifying and removing any stored XSS payloads from the message database. Note that restricting endpoint access may impact legitimate functionality if messages are intended to be user-submitted.