dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-39598

HIGH · 8.0 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
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
Unrestricted Upload of File with Dangerous Type vulnerability in Kodezen LLC Academy LMS Pro allows Upload a Web Shell to a Web Server. This issue affects Academy LMS Pro: from n/a before 3.5.2.

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

Academy LMS Pro has an unrestricted file upload vulnerability that allows authenticated attackers to upload executable files (such as PHP web shells) to the web server. Since the application does not properly validate file types or sanitize uploaded files, uploaded scripts can be accessed and executed through the web server, enabling remote code execution.

MitigationUpgrade to Academy LMS Pro version 3.5.2 or later, which should contain proper file validation. Additionally, implement strict allowlist-based file type validation, store uploads outside the web root, disable script execution in upload directories, and rename uploaded files to prevent direct execution.

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

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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. Identify Academy LMS Pro installation and version
    Locate the Academy LMS Pro installation directory and check the version file or admin panel for the installed version number
    Affected if The installed version is lower than 3.5.2
  2. Verify user authentication is enabled
    Check if the application has user registration and login functionality enabled in the system configuration
    Affected if Authentication is enabled, allowing authenticated users to access the upload feature
  3. Locate the file upload functionality
    Navigate to the user/teacher dashboard and identify any file upload features (assignment submissions, profile pictures, course materials, etc.)
    Affected if File upload functionality exists and is accessible to authenticated users
  4. Examine upload directory placement
    Check the web server configuration and upload directory path to determine if uploaded files are stored within the web root (public_html, htdocs, etc.)
    Affected if Uploaded files are stored in a web-accessible directory and can be accessed via HTTP/HTTPS
  5. Check for server-side file type validation
    Review the application's upload handling code or configuration settings to determine if file type validation is implemented (check for allowed extensions, MIME type checking, or content analysis)
    Affected if No server-side file type validation exists or can be easily bypassed

A user is affected if Academy LMS Pro version is below 3.5.2 AND authenticated user access to file upload exists AND uploaded files are stored in a web-accessible location without proper validation.

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

Upgrade to Academy LMS Pro version 3.5.2 or later, which should contain proper file validation. Additionally, implement strict allowlist-based file type validation, store uploads outside the web root, disable script execution in upload directories, and rename uploaded files to prevent direct execution.

Recommended fix Moderate confidence

Academy LMS Pro version 3.5.2

  1. 1. Create a complete backup of your WordPress site, including database and all files, before making any changes.
  2. 2. Navigate to your WordPress admin dashboard and go to Plugins > Installed Plugins.
  3. 3. Find Academy LMS Pro in the plugins list and check if an update is available.
  4. 4. If an update to version 3.5.2 is available, click 'Update Now' to apply the security patch.
  5. 5. Alternatively, if automatic updates are not available, manually download Academy LMS Pro version 3.5.2 from the vendor and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version shows 3.5.2 in your plugins list.
  7. 7. Test critical LMS functionality (course creation, student enrollment, quiz submissions) to ensure the update did not break existing features.
Caveat Minor: Test LMS workflows after upgrade as with any plugin update; no major breaking changes documented

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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