dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-4800

HIGH · 8.8 CVSS v3.1 Published 2025-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The MasterStudy LMS Pro plugin for WordPress is vulnerable to arbitrary file uploads due to a missing file type validation in the stm_lms_add_assignment_attachment function in all versions up to, and including, 4.7.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server, which may make remote code execution possible.

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 confidence

The MasterStudy LMS Pro WordPress plugin contains an arbitrary file upload vulnerability in the stm_lms_add_assignment_attachment function due to missing file type validation. Authenticated users with Subscriber-level access can upload arbitrary files to the server, potentially achieving remote code execution.

MitigationUpdate MasterStudy LMS Pro to version 4.7.1 or later which contains proper file type validation. If immediate patching is not feasible, consider restricting assignment upload capabilities or temporarily disabling the assignment feature until the patch can be applied.

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Check MasterStudy LMS Pro plugin version
    Locate the plugin in wp-content/plugins and inspect the main plugin file header or readme.txt for the Version field. Alternatively, query the WordPress database: SELECT option_value FROM wp_options WHERE option_name LIKE '%masterstudy%version%';
    Affected if Version is lower than 4.7.1 (vulnerable range not specified, but versions prior to the 4.7.1 fix are considered affected)
  2. Verify the assignment upload feature is enabled
    Navigate to WordPress admin > MasterStudy LMS > Settings > Assignments (or similar path based on plugin structure). Check if assignment uploads are permitted. Alternatively, search the database for assignment-related settings: SELECT option_value FROM wp_options WHERE option_name LIKE '%stm_lms_assignment%';
    Affected if Assignment upload functionality is enabled (this feature must be active for the vulnerable code path to be reachable)
  3. Confirm subscriber-level user access exists
    Check WordPress user roles: go to Users > Roles in admin, or inspect wp_options for role capabilities. Verify if the 'subscriber' role retains standard capabilities. Query: SELECT meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%subscriber%';
    Affected if Subscriber role exists and is not restricted from accessing the LMS assignment functionality
  4. Locate the vulnerable upload handler
    Search the plugin directory (wp-content/plugins/stm-lms-pro) for the file containing 'stm_lms_add_assignment_attachment' function. Inspect the code to confirm missing file type validation. Use grep or inspect the plugin files directly.
    Affected if The function exists in the installed plugin version without proper file type validation

The environment is affected if MasterStudy LMS Pro version is below 4.7.1 AND the assignment upload feature is enabled AND subscriber-level users have access to the LMS assignment functionality.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update MasterStudy LMS Pro to version 4.7.1 or later which contains proper file type validation. If immediate patching is not feasible, consider restricting assignment upload capabilities or temporarily disabling the assignment feature until the patch can be applied.

Recommended fix Moderate confidence

MasterStudy LMS Pro version 4.7.1 or latest available version

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the MasterStudy LMS Pro plugin in the plugin list
  4. 4. Check the current installed version of the plugin (displayed under the plugin name)
  5. 5. If the installed version is 4.7.0 or lower, update the plugin to the latest available version
  6. 6. After updating, verify the new version number reflects the update
  7. 7. Test the assignment upload functionality to confirm the plugin continues to work correctly
Caveat Review the plugin's changelog for any breaking changes between your current version and the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4800 — 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-4800 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