Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-59666 Overview
CVE-2026-59666 is a Cross-Site Scripting (XSS) vulnerability [CWE-79] affecting the Repasat application. The flaw resides in the nomOrigen parameter processed by the /es/origins/store endpoint. An attacker who tricks an authenticated user into submitting a crafted request can execute arbitrary JavaScript in the victim's browser session. The Spanish National Cybersecurity Institute (INCIBE) issued a security notice covering this and related issues in Repasat.
Critical Impact
Successful exploitation allows attackers to execute arbitrary script code in a victim's browser, enabling session theft, credential harvesting, and unauthorized actions performed in the user's context.
Affected Products
- Repasat application (vendor-specific version not published in the NVD record)
- Endpoint: /es/origins/store
- Parameter: nomOrigen
Discovery Timeline
- 2026-10-02 - CVE CVE-2026-59666 published to NVD
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-59666
Vulnerability Analysis
The vulnerability is a reflected or stored Cross-Site Scripting flaw within the Repasat application's origin management workflow. The nomOrigen parameter submitted to /es/origins/store is incorporated into application output without proper encoding or sanitization. When an authenticated user views affected content, the browser interprets attacker-controlled input as executable script.
Exploitation requires low privileges and user interaction, limiting mass exploitation but still enabling targeted attacks against authenticated users. The confidentiality and integrity impact is limited to the browser context of the victim user, consistent with typical client-side script injection.
Root Cause
The root cause is improper neutralization of input during web page generation [CWE-79]. The application fails to sanitize or contextually encode user-supplied values in the nomOrigen parameter before rendering them in HTML output. Any user capable of submitting origin records can inject HTML or JavaScript payloads.
Attack Vector
An attacker with a low-privileged authenticated account submits a crafted value in the nomOrigen field through the /es/origins/store endpoint. The payload is stored or reflected and later rendered in the browser of a victim user who accesses the affected view. Delivery typically relies on social engineering, such as a link or form submission the victim is persuaded to trigger.
No verified public exploit code is available. The vulnerability is described in the INCIBE Security Notice on Vulnerabilities.
Detection Methods for CVE-2026-59666
Indicators of Compromise
- HTTP POST requests to /es/origins/store containing script tags, event handlers, or URL-encoded JavaScript in the nomOrigen parameter.
- Unexpected outbound requests from user browsers to attacker-controlled domains following access to Repasat origin pages.
- Session cookies or authentication tokens appearing in web server referrer logs or external telemetry.
Detection Strategies
- Deploy web application firewall (WAF) rules that inspect the nomOrigen parameter for XSS payload patterns such as <script>, onerror=, javascript:, and encoded variants.
- Review application access logs for anomalous payloads submitted to the /es/origins/store endpoint by low-privileged accounts.
- Enable Content Security Policy (CSP) violation reporting to surface inline script execution attempts on Repasat pages.
Monitoring Recommendations
- Correlate authenticated session activity with HTTP request bodies containing HTML tags or scripting syntax submitted to origin endpoints.
- Monitor for unusual Document Object Model (DOM) modifications or outbound XHR requests in browser telemetry when users access Repasat.
- Alert on repeated submissions of origin records containing non-printable or heavily encoded characters.
How to Mitigate CVE-2026-59666
Immediate Actions Required
- Apply vendor-supplied patches or updates for the Repasat application as referenced in the INCIBE advisory.
- Restrict access to the /es/origins/store endpoint to trusted users until a fix is validated.
- Audit stored origin records for existing malicious payloads and sanitize or remove affected entries.
Patch Information
Consult the INCIBE Security Notice on Vulnerabilities for vendor remediation guidance. The NVD record does not list specific fixed versions as of the publication date.
Workarounds
- Deploy WAF rules that block script-like content in the nomOrigen parameter of requests to /es/origins/store.
- Enforce a strict Content Security Policy that disallows inline scripts and restricts script sources to trusted origins.
- Enable the browser HttpOnly and Secure flags on session cookies to limit the impact of script injection on session theft.
- Train authenticated users to avoid following untrusted links to the Repasat application while a vendor patch is pending.
# Example nginx WAF-style configuration to block common XSS payloads on the affected endpoint
location /es/origins/store {
if ($request_method = POST) {
if ($request_body ~* "(<script|onerror=|onload=|javascript:|%3Cscript)") {
return 403;
}
}
proxy_pass http://repasat_backend;
}
# Content Security Policy header to mitigate script execution
add_header Content-Security-Policy "default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self';" always;
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

