# CVE-2025-3400: ESAFENET CDG UnChkMailApplication.jsp sql injection

> Remote attackers can exploit SQL injection in UnChkMailApplication.jsp to read or modify database contents.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-vcpm-vcmc-m56v

## What is CVE-2025-3400?

CVE-2025-3400 is a medium-severity SQL injection vulnerability in Esafenet Cdg, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in ESAFENET CDG 5.6.3.154.205_20250114. This affects an unknown part of the file /client/UnChkMailApplication.jsp. The manipulation of the argument typename leads to sql injection. It is possible to initiate 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-3400?

It affects 1 product.


Products: Esafenet Cdg.

## How do I fix CVE-2025-3400?

No fix has been published for CVE-2025-3400 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3400 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3400 exists.

## Other vulnerabilities in Esafenet Cdg

- [CVE-2024-42885](https://insights.sbomify.com/CVE-2024-42885/): SQL injection in n/a (critical 9.1)
- [CVE-2024-46510](https://insights.sbomify.com/CVE-2024-46510/): SQL injection in n/a (high 7.6)
- [CVE-2017-18636](https://insights.sbomify.com/CVE-2017-18636/): Path traversal in n/a (high 7.5)
- [CVE-2025-3399](https://insights.sbomify.com/CVE-2025-3399/): ESAFENET CDG updateNotice.jsp sql injection (medium 6.9)
- [CVE-2025-3401](https://insights.sbomify.com/CVE-2025-3401/): ESAFENET CDG getLimitIPList.jsp sql injection (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3400 and fix it if it is affected.

What it is: CVE-2025-3400 is a medium-severity SQL injection vulnerability in Esafenet Cdg, published on 8 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3400 exists.

Affected product: Esafenet Cdg. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3400/ (Markdown: https://insights.sbomify.com/CVE-2025-3400/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3400
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3400
- OSV: https://osv.dev/vulnerability/CVE-2025-3400

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3400/
Summaries are generated and may contain mistakes; the official description above is the record.
