# CVE-2025-9399: YiFang CMS L_tool.php sql injection

> Remote attackers can exploit SQL injection in YiFang CMS via the new_url argument 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/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:** 25 Aug 2025
- **Updated:** 25 Aug 2025
- **Also known as:** GHSA-x9w6-w79w-w3r4

## What is CVE-2025-9399?

CVE-2025-9399 is a medium-severity SQL injection vulnerability in YiFang CMS, published on 25 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in YiFang CMS up to 2.0.5. Affected by this issue is some unknown functionality of the file app/logic/L_tool.php. The manipulation of the argument new_url results in sql injection. The attack may be launched remotely. The exploit is now 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-9399?

It affects 1 product.


Products: Wanglongcn Yifang.

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

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

## Is CVE-2025-9399 being exploited?

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

## Other vulnerabilities in YiFang CMS

- [CVE-2025-45887](https://insights.sbomify.com/CVE-2025-45887/): Server-side request forgery in n/a (critical 9.1)
- [CVE-2025-9398](https://insights.sbomify.com/CVE-2025-9398/): YiFang CMS Migrate.php exportInstallTable information disclosure (medium 6.9)
- [CVE-2025-9400](https://insights.sbomify.com/CVE-2025-9400/): YiFang CMS P_file.php mergeMultipartUpload unrestricted upload (medium 5.3)
- [CVE-2025-11136](https://insights.sbomify.com/CVE-2025-11136/): YiFang CMS Backend File.php webUploader unrestricted upload (medium 5.1)
- [CVE-2025-5381](https://insights.sbomify.com/CVE-2025-5381/): Yifang CMS Admin Panel downloadFile path traversal (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9399 is a medium-severity SQL injection vulnerability in YiFang CMS, published on 25 Aug 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-9399 exists.

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

## Sources

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

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