# CVE-2025-5107: Fujian Kelixun xml_cdr_details.php sql injection

> Remote attackers can exploit SQL injection in Kelixun's xml_cdr_details.php via the uuid parameter to read or modify database contents.

- **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`)
- **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:** 23 May 2025
- **Updated:** 27 May 2025
- **Also known as:** GHSA-5h4m-f9x8-8ffh

## What is CVE-2025-5107?

CVE-2025-5107 is a medium-severity SQL injection vulnerability in Fujian Kelixun, published on 23 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Fujian Kelixun 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /app/xml_cdr/xml_cdr_details.php. The manipulation of the argument uuid leads to sql injection. The attack can be initiated 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-5107?

It affects 1 product.


Products: Kirisun Fujian Kelixun.

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

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

## Is CVE-2025-5107 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5107 is a medium-severity SQL injection vulnerability in Fujian Kelixun, published on 23 May 2025. 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-2025-5107 exists.

Affected product: Fujian Kelixun. 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-5107/ (Markdown: https://insights.sbomify.com/CVE-2025-5107/index.md)
```

## Sources

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

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