LearnpressWordPress extension · Thimpress
CVE-2024-2115
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 · uneditedThe LearnPress – WordPress LMS Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.0.0. This is due to missing or incorrect nonce validation on the filter_users functions. This makes it possible for unauthenticated attackers to elevate their privileges to that of a teacher via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 confidenceThe LearnPress WordPress LMS plugin has a CSRF vulnerability in its filter_users functions due to missing nonce validation. This allows unauthenticated attackers to trick administrators into unknowingly submitting forged requests that grant the attacker teacher-level privileges on the site.
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
< 4.0.1CVSS 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
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify LearnPress plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and find LearnPress. Note the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/learnpress/ via file system or FTP.Affected if The installed version is any version prior to 4.0.1 (e.g., 4.0.0, 3.x.x, etc.)
-
Confirm plugin file existenceAccess the site via FTP or file manager and verify the /wp-content/plugins/learnpress/ directory exists and contains the plugin files, particularly includes/admin/class-lp-admin-users.php or similar filter_users related files.Affected if The learnpress plugin directory exists on the server with any version below 4.0.1
-
Inspect for unauthorized teacher accountsIn WordPress admin, go to LearnPress > Users > Teachers or Users > All Users and review the list for any unknown or suspicious teacher accounts that were not created by legitimate administrators.Affected if New teacher accounts exist that were not intentionally created by known administrators
-
Check user roles and capabilitiesNavigate to Users > All Users and examine the role column. Look for any users with 'Instructor' or 'Teacher' roles that should not have those privileges, or check the wp_usermeta table for capability changes.Affected if Users have teacher/instructor roles or elevated capabilities that were not explicitly granted by the site administrator
The environment is affected if LearnPress plugin version is below 4.0.1, as the missing nonce validation in filter_users functions allows CSRF-based privilege escalation to teacher roles.
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.
dbcve · scoped4.0.1
Update LearnPress to version 4.0.1 or later which includes proper nonce validation for the filter_users functions to prevent CSRF attacks.
4.0.1
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate LearnPress (LearnPress – WordPress LMS Plugin) in the plugin list
- Click 'Update now' when version 4.0.1 is available, or manually download and upload version 4.0.1 from the WordPress plugin repository
- Verify the plugin version shows 4.0.1 after updating
- Test critical LearnPress functionality (course creation, user enrollment) to ensure the update did not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Learnpress
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2115 — 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-2024-2115 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