# CVE-2026-4173: CodePhiliaX Chat2DB Database Export DMDBManage.java updateProcedure sql injection

> Remote attackers can execute arbitrary SQL commands via the database export handler in Chat2DB, potentially reading or modifying data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2026
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-cxhh-3495-hr7r

## What is CVE-2026-4173?

CVE-2026-4173 is a medium-severity SQL injection vulnerability in CodePhiliaX Chat2DB, published on 15 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in CodePhiliaX Chat2DB up to 0.3.7. This vulnerability affects the function exportTable/exportTableColumnComment/exportView/exportProcedure/exportTriggers/exportTrigger/updateProcedure of the file DMDBManage.java of the component Database Export Handler. This manipulation causes sql injection. It is possible to initiate the attack remotely. The exploit has been published 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-2026-4173?


## How do I fix CVE-2026-4173?

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

## Is CVE-2026-4173 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4173 and fix it if it is affected.

What it is: CVE-2026-4173 is a medium-severity SQL injection vulnerability in CodePhiliaX Chat2DB, published on 15 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4173 exists.

Affected product: CodePhiliaX Chat2DB. 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-2026-4173/ (Markdown: https://insights.sbomify.com/CVE-2026-4173/index.md)
```

## Sources

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

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