CVE-2025-1844
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 · uneditedA vulnerability, which was classified as critical, was found in ESAFENET CDG 5.6.3.154.205_20250114. Affected is an unknown function of the file /CDGServer3/logManagement/backupLogDetail.jsp. The manipulation of the argument logTaskId leads to sql injection. It is possible to launch the attack 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 confidenceSQL injection vulnerability in ESAFENET CDG 5.6.3.154.205_20250114 allows remote attackers to inject malicious SQL queries via the logTaskId parameter in the /CDGServer3/logManagement/backupLogDetail.jsp file. The critical CVSS score of 9.8 indicates potential for complete system compromise through database exploitation.
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= 5.6.3.154.205_20250114CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Esafenet Cdg installation and versionLocate the Esafenet Cdg installation directory and check the version file or product information. Common locations include the installation root folder or system information panels within the application.Affected if The installed version is exactly 5.6.3.154.205_20250114
-
Verify vulnerable JSP file existsCheck for the presence of /CDGServer3/logManagement/backupLogDetail.jsp in the web application root directory. This file should exist in the deployed application.Affected if The backupLogDetail.jsp file exists in the expected path under the CDGServer3 web application directory
-
Confirm the logTaskId parameter is in useReview the backupLogDetail.jsp source code to verify it accepts and processes a logTaskId parameter without proper sanitization. Check if this parameter is directly used in database queries.Affected if The logTaskId parameter is present in the JSP and is used in SQL queries without parameterized queries or input validation
-
Test endpoint accessibilityVerify the endpoint /CDGServer3/logManagement/backupLogDetail.jsp is accessible over the network. This may require checking web server configuration or attempting a request to the endpoint.Affected if The vulnerable endpoint is exposed and reachable from the network
If Esafenet Cdg version 5.6.3.154.205_20250114 is installed and the backupLogDetail.jsp file with the vulnerable logTaskId parameter is present and accessible, the environment is affected by CVE-2025-1844.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement parameterized queries or prepared statements in backupLogDetail.jsp to sanitize the logTaskId parameter, or apply vendor patch if available; until fix is applied, consider disabling the affected endpoint or implementing WAF rules as temporary mitigation.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1844 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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