# CVE-2025-0331: YunzMall HTTP POST Request ResetpwdController.php changePwd password recovery

> Attackers can bypass password recovery controls in YunzMall to take over accounts via manipulated POST requests.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2025
- **Updated:** 9 Jan 2025
- **Also known as:** GHSA-h363-2pf8-49mq

## What is CVE-2025-0331?

CVE-2025-0331 is a medium-severity authentication bypass vulnerability in YunzMall, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in YunzMall up to 2.4.2. This issue affects the function changePwd of the file /app/platform/controllers/ResetpwdController.php of the component HTTP POST Request Handler. The manipulation of the argument pwd leads to weak password recovery. The attack may 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-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2025-0331 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0331 is a medium-severity authentication bypass vulnerability in YunzMall, published on 9 Jan 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-0331 exists.

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

## Sources

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

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