dbcve.org
CdgApplication · Esafenet

CVE-2025-0788

HIGH · 8.8 CVSS v3.1 Published 2025-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in ESAFENET CDG V5. It has been rated as critical. Affected by this issue is some unknown functionality of the file /content_top.jsp. The manipulation of the argument id leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in ESAFENET CDG V5's /content_top.jsp file. The 'id' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands. This could allow unauthorized database access, data exfiltration, or potentially remote code execution depending on database configuration.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the id parameter. Implement strict input validation and consider deploying a WAF rule as a temporary protective measure until the code fix is deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CdgApplication
Affected:= 5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Esafenet Cdg V5 installation
    Check the system for Esafenet Cdg V5 installation directories or running services. Look for application logs, installation folders, or running processes related to 'cdg' or 'esafenet'.
    Affected if Esafenet Cdg V5 is installed on the system
  2. Locate the vulnerable JSP file
    Search the web application directory for the file /content_top.jsp. Common paths include webapp or htdocs folders within the application installation directory.
    Affected if The file /content_top.jsp exists in the application web root
  3. Inspect the id parameter handling
    Open content_top.jsp and examine how the 'id' parameter is processed. Search for code that uses the id parameter directly in SQL query strings without using prepared statements or parameter binding.
    Affected if The 'id' parameter is used in SQL queries without parameterized queries or input sanitization
  4. Verify application exposure
    Check if the web application is accessible and the /content_top.jsp endpoint is reachable via HTTP/HTTPS requests.
    Affected if The vulnerable endpoint is accessible from the network

The environment is affected if Esafenet Cdg V5 is running and the /content_top.jsp file contains unsanitized 'id' parameter usage in SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements for the id parameter. Implement strict input validation and consider deploying a WAF rule as a temporary protective measure until the code fix is deployed.

Recommended fix Low confidence
  1. Implement input validation and sanitization on all user-supplied parameters, especially the 'id' parameter in /content_top.jsp
  2. Replace dynamic SQL queries with parameterized queries (prepared statements) to prevent SQL injection
  3. Deploy a Web Application Firewall (WAF) as an interim mitigation to block SQL injection attacks
  4. Restrict network access to the affected application to limit remote attack surface
  5. Audit application code for additional SQL injection vulnerabilities in other files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cdg Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0788 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0788 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data