CVE-2025-31340
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 · uneditedA improper control of filename for include/require statement in PHP program vulnerability in the retrieve course Information function of Wisdom Master Pro versions 5.0 through 5.2 allows remote attackers to perform arbitrary system commands by running 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 · high confidenceThis is a Local File Inclusion (LFI) vulnerability in the 'retrieve course Information' function of Wisdom Master Pro PHP application (versions 5.0-5.2). Improper control of filename parameters in include/require statements allows remote attackers to execute arbitrary system commands by including and executing malicious files.
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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Wisdom Master Pro installation and versionLocate the application and determine its installed version number. This is typically found in the software's main file, version configuration, or admin interface. Compare the found version against the affected range 5.0-5.2.Affected if The installed version falls within 5.0 to 5.2 inclusive.
-
Locate the retrieve course Information functionSearch the application codebase for the 'retrieve course Information' function or similar naming variants. Identify the PHP file containing this function and its code logic.Affected if The function exists in the codebase and is accessible via web request or application logic.
-
Inspect the function for dynamic file inclusionExamine the retrieve course Information function code for include, require, include_once, or require_once statements that process user-supplied input. Determine if parameters passed to the function are directly used in these inclusion statements without sanitization.Affected if The function uses include/require statements that incorporate user input without proper validation or sanitization.
-
Verify user input reaches the inclusion pointTrace how parameters flow from user request (GET/POST) through the application to the include/require statement in the retrieve course Information function. Confirm that attacker-controllable values can reach the file inclusion logic.Affected if User-supplied input from HTTP requests can be passed to the include/require statement without filtering.
The environment is affected if Wisdom Master Pro versions 5.0-5.2 is installed and the retrieve course Information function uses include/require with unsanitized user input, allowing path traversal and arbitrary file inclusion.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version if available; otherwise, implement strict input validation with whitelist approach on file inclusion parameters, disable allow_url_include, and restrict PHP open_basedir. Consider disabling the vulnerable function until patched.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-31340 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31340 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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