# CVE-2025-56162: SQL injection in n/a

> Unauthenticated SQL injection in YOSHOP allows attackers to dump database data and potentially execute remote code via web shells or xp_cmdshell.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2025
- **Updated:** 2 Oct 2025
- **Also known as:** GHSA-wfc7-vvw3-2pq2

## What is CVE-2025-56162?

CVE-2025-56162 is a medium-severity SQL injection vulnerability in n/a, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

YOSHOP 2.0 suffers from an unauthenticated SQL injection in the goodsIds parameter of the /api/goods/listByIds endpoint. The getListByIds function concatenates user input into orderRaw('field(goods_id, ...)'), allowing attackers to: (a) enumerate or modify database data, including dumping admin password hashes; (b) write web-shell files or invoke xp_cmdshell, leading to remote code execution on servers configured with sufficient DB privileges.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Yiovo Firefly Mall.

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

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

## Is CVE-2025-56162 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-56161](https://insights.sbomify.com/CVE-2025-56161/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56162 is a medium-severity SQL injection vulnerability in n/a, published on 2 Oct 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-56162 exists.

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

## Sources

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

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