# CVE-2025-56161: Information disclosure in n/a

> Unauthenticated attackers can access sensitive user data including password hashes and financial details via exposed API endpoints in YOSHOP.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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-m7xp-q497-c5g4

## What is CVE-2025-56161?

CVE-2025-56161 is a high-severity 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 allows unauthenticated information disclosure via comment-list API endpoints in the Goods module. The Comment model eagerly loads the related User model without field filtering; because User.php defines no $hidden or $visible attributes, sensitive fields (bcrypt password hash, mobile number, pay_money, expend_money.) are exposed in JSON responses. Route names vary per deployment (e.g. /api/goods.pinglun/list), but all call the same vulnerable model logic.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Yiovo Firefly Mall.

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

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

## Is CVE-2025-56161 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-56162](https://insights.sbomify.com/CVE-2025-56162/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56161 is a high-severity 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-56161 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-56161/ (Markdown: https://insights.sbomify.com/CVE-2025-56161/index.md)
```

## Sources

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

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