dbcve.org
LearnpressWordPress extension · Thimpress

CVE-2024-4397

HIGH · 8.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 4.2.6.6 or later.
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 LearnPress – WordPress LMS Plugin plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'save_post_materials' function in versions up to, and including, 4.2.6.5. This makes it possible for authenticated attackers, with Instructor-level permissions 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 LearnPress WordPress LMS plugin fails to validate file types in the save_post_materials function, allowing authenticated instructors to upload arbitrary files. This enables remote code execution by uploading malicious PHP files that can then be executed on the server.

MitigationUpdate LearnPress to version 4.2.6.6 or later which contains proper file type validation. Until then, restrict instructor-level permissions to trusted users only.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LearnpressWordPress extension
Affected:< 4.2.6.6

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. Verify LearnPress is installed
    Check your WordPress plugins dashboard or inspect the /wp-content/plugins/learnpress/ directory for the plugin
    Affected if LearnPress plugin is present on the WordPress site
  2. Check installed LearnPress version
    Look in the plugin header (plugins.php in WordPress admin, or version.php in the plugin folder) to find the exact version number
    Affected if Version is lower than 4.2.6.6 (for example 4.2.5, 4.2.0, etc.)
  3. Confirm instructor role exists
    Navigate to WordPress Users > Users List and filter by 'Instructor' role, or check Users > User Roles for an 'Instructor' capability
    Affected if There are users with instructor-level permissions on the site
  4. Verify materials functionality is accessible
    Check if a user with instructor role can access LearnPress materials (usually at /wp-admin/post-new.php?post_type=lp_material or similar)
    Affected if Instructors can access and create material posts without restrictions
  5. Scan for suspicious uploads
    Search the /wp-content/uploads/learnpress/ directory (or custom upload path) for unexpected .php, .phtml, or .exe files
    Affected if Any PHP files or executable files are found in the learnpress upload directories

You are affected if LearnPress is installed with a version below 4.2.6.6 AND instructor-level users exist on your site with access to the materials upload feature.

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
Upgrade available Upgrade to 4.2.6.6 or later
Fixed in 4.2.6.6
Interim mitigation

Update LearnPress to version 4.2.6.6 or later which contains proper file type validation. Until then, restrict instructor-level permissions to trusted users only.

Recommended fix High confidence

4.2.6.6

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate LearnPress (LearnPress – WordPress LMS Plugin) in the plugin list
  4. 4. Check if the current version is below 4.2.6.6
  5. 5. If an update is available, click 'Update Now' to update to version 4.2.6.6 or later
  6. 6. Alternatively, download LearnPress version 4.2.6.6 or later from the official WordPress plugin repository
  7. 7. Deactivate the existing LearnPress plugin, delete it, then upload and install the updated version
  8. 8. After update, verify the version number reflects 4.2.6.6 or higher

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

Fix this in Learnpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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