CVE-2026-2102
Deferred Deferred - Pending Action

Reflected XSS in Wren Security Commons CREST Framework

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: b6ef82d7-f637-461b-aedd-74f5857d5f5b

Description
wrensec-commons contains a reflected cross-site scripting (XSS) vulnerability in the CREST framework's HTTP binding. The HttpUtils.prepareResponse() method used the _mimeType request parameter to set the Content-Type response header without proper sanitization. By sending a GET request with _mimeType=text/html, an attacker could cause the browser to interpret a CREST JSON response as HTML, enabling execution of arbitrary JavaScript in the victim's browser. The vulnerability is exploitable by tricking a user into visiting a crafted URL targeting any deployed CREST endpoint. The issue is fixed in versions 22.6.2 and 23.0.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-02
Last Modified
2026-11-02
Generated
2026-11-02
AI Q&A
2026-11-02
EPSS Evaluated
N/A
NVD
CVE-2026-2102

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
Wren Security wrensec-commons 0
Wren Security wrensec-commons 23.0.0-M1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a reflected cross-site scripting (XSS) vulnerability in the wrensec-commons library's CREST framework. It occurs because the HttpUtils.prepareResponse() method uses the _mimeType request parameter to set the Content-Type response header without proper sanitization. An attacker can exploit this by sending a crafted URL with _mimeType=text/html, causing the browser to interpret a JSON response as HTML and execute arbitrary JavaScript in the victim's browser.

Detection Guidance

To detect this XSS vulnerability, inspect HTTP responses from CREST endpoints for improper Content-Type headers. Check if the _mimeType parameter in GET requests influences the response header without sanitization. Use tools like curl to send test requests with _mimeType=text/html and verify if the response header sets Content-Type:text/html without proper escaping.

Impact Analysis

An attacker could trick you into clicking a malicious link, leading to unauthorized script execution in your browser. This could allow theft of session cookies, sensitive data, or redirection to phishing sites. The impact depends on your use of CREST endpoints and the privileges of the authenticated user.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, potentially violating GDPR's data protection requirements or HIPAA's security rules for protected health information. Organizations using affected systems may face compliance violations if exploited.

Mitigation Strategies

Upgrade wrensec-commons to version 22.6.2 or later. If upgrading is not immediately possible, implement input validation to sanitize the _mimeType parameter and ensure the Content-Type header is set to application/json by default. Additionally, restrict access to CREST endpoints to trusted users only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-2102. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...