CVE Intelligence
Skip to main content
mediumCross-site Scripting

CVE-2026-59670

CVE-2026-59670 — Multiple vulnerabilities in the Repasat application

Cross-Site Scripting vulnerability in the Repasat application. Successful exploitation of this vulnerability could allow an attacker to trick a user into executing arbitrary code in the victim’s browser. The “nomListaValidacion” parameter is affected – endpoint “/es/validationslists/assignList/Employee/45659”.

Published Updated Sources: NVD, Repasat (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

ahead of 0% of scored CVEs

Affects

Repasat

Repasat application

CVSS base

4.8

medium

Remediation

The vendor's own words where we have them.

The vulnerabilities have been fixed in the April patch version ‘20260402’.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
RepasatRepasat application0Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Scope

X

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

A

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
4.8CVSS 4.0medium——Repasat (CNA)

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

  • Bypass Protection Mechanism
  • Read Application Data
  • Execute Unauthorized Code or Commands

Mitigation: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.

Weakness & attack patterns

  • CWE-79Cross-site Scripting

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-85 · AJAX FingerprintingCAPEC-592 · Stored XSSCAPEC-591 · Reflected XSSCAPEC-63 · Cross-Site Scripting (XSS)CAPEC-588 · DOM-Based XSSCAPEC-209 · XSS Using MIME Type Mismatch

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /es/validationslists/assignList/Employee/45659.
  • Prioritize edge telemetry for network-reachable Repasat application.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 4.8 (AV:N)

    Oct 2, 2026 · NVD

  3. Initial · CVE published

    Oct 2, 2026 · NVD

  4. Added · GHSA-2r4w-823m-crf4 published (medium)

    Oct 2, 2026 · GitHub Security Advisory

  5. CVE published by NIST.

    Oct 2, 2026 · SOCRadar CTI

References

3 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-59670 is Multiple vulnerabilities in the Repasat application, a medium vulnerability affecting Repasat application from Repasat. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-59670. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-59670. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 4.8 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.