# CVE-2025-9273: CData API Server MySQL Misconfiguration Information Disclosure Vulnerability

> Remote authenticated attackers can disclose sensitive local files via MySQL client configuration in CData API Server.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 2 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-p4rq-6jpq-3wqj

## What is CVE-2025-9273?

CVE-2025-9273 is a medium-severity vulnerability in CData API Server, published on 2 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CData API Server MySQL Misconfiguration Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of CData API Server. Authentication is required to exploit this vulnerability.

The specific flaw exists within the usage of MySQL connections. When connecting to a MySQL server, the product enables an option that gives the MySQL server permission to request local files from the MySQL client. An attacker can leverage this vulnerability to disclose information in the context of NETWORK SERVICE. Was ZDI-CAN-23950.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

It affects 1 product.


Products: Cdata Api Server.

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

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

## Is CVE-2025-9273 being exploited?

There is no known exploitation of CVE-2025-9273 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9273 is a medium-severity vulnerability in CData API Server, published on 2 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9273 in the wild and no public exploit code.

Affected product: CData API Server. 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-9273/ (Markdown: https://insights.sbomify.com/CVE-2025-9273/index.md)
```

## Sources

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

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