# CVE-2025-31339: Wisdom Master Pro - Unrestricted Upload of File with Dangerous Type

> Remote authenticated users can upload malicious files in Wisdom Master Pro, potentially leading to code execution.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/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:** 17 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-9279-xrgq-m4hp

## What is CVE-2025-31339?

CVE-2025-31339 is a medium-severity vulnerability in SUNNET Technology Co., Ltd. Wisdom Master Pro, published on 17 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An unrestricted upload of file with dangerous type vulnerability in the course management function of Wisdom Master Pro versions 5.0 through 5.2 allows remote authenticated users to craft a malicious file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-31339 being exploited?

There is no known exploitation of CVE-2025-31339 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31339 is a medium-severity vulnerability in SUNNET Technology Co., Ltd. Wisdom Master Pro, published on 17 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31339 in the wild and no public exploit code.

Affected product: SUNNET Technology Co., Ltd. Wisdom Master Pro. 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-31339/ (Markdown: https://insights.sbomify.com/CVE-2025-31339/index.md)
```

## Sources

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

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