dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-31339

MEDIUM · 5.3 CVSS v4.0 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Wisdom Master Pro versions 5.0-5.2 contains an unrestricted file upload vulnerability in its course management function. Authenticated users can upload files with dangerous types (e.g., executable scripts) without proper validation, potentially allowing arbitrary code execution on the server.

MitigationImplement strict allowlist-based file type validation (checking magic bytes/MIME type, not just extensions), store uploads outside the web root, rename files upon upload, and serve user files through a separate domain or sandboxed environment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Wisdom Master Pro installation
    Locate the Wisdom Master Pro application on your system and confirm it is installed
    Affected if Wisdom Master Pro is present on the system
  2. Verify the installed version
    Check the installed version of Wisdom Master Pro and compare it to the affected range of 5.0 through 5.2
    Affected if The installed version is 5.0, 5.1, or 5.2
  3. Confirm course management module is active
    Determine whether the course management function is enabled and accessible to users in your deployment
    Affected if The course management module is enabled and accessible
  4. Check file upload capability in course management
    Inspect the course management function to confirm file upload functionality exists and is available to authenticated users
    Affected if Authenticated users can access a file upload feature within course management
  5. Inspect file type validation controls
    Examine the file upload mechanism to determine if there are restrictions on file types (e.g., checking for extensions, MIME types, or magic bytes)
    Affected if No file type validation exists or validation can be bypassed allowing executable file types

You are affected if Wisdom Master Pro version 5.0, 5.1, or 5.2 is installed with the course management function enabled and accessible to authenticated users without proper file type validation on uploads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based file type validation (checking magic bytes/MIME type, not just extensions), store uploads outside the web root, rename files upon upload, and serve user files through a separate domain or sandboxed environment.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31339 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31339 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data