# CVE-2025-31338: Wisdom Master Pro - Missing Authorization

> Remote attackers can access the API to obtain partial user data due to missing authorization in the teacher information retrieval function.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/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:** 17 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-xjjj-rcfc-fp6h

## What is CVE-2025-31338?

CVE-2025-31338 is a medium-severity missing authorization vulnerability in SUNNET Technology Co., Ltd. Wisdom Master Pro, published on 17 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing authorization vulnerability in the retrieve teacher Information function of Wisdom Master Pro versions 5.0 through 5.2 allows remote attackers to obtain partial user data by accessing the API functionality.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-31338 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31338 is a medium-severity missing authorization vulnerability in SUNNET Technology Co., Ltd. Wisdom Master Pro, published on 17 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31338 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-31338/ (Markdown: https://insights.sbomify.com/CVE-2025-31338/index.md)
```

## Sources

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

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