CVE-2024-39642
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 · uneditedAuthorization Bypass Through User-Controlled Key vulnerability in ThimPress LearnPress allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects LearnPress: from n/a through 4.2.6.8.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 · moderate confidenceLearnPress WordPress plugin versions up to 4.2.6.8.2 contain an authorization bypass vulnerability where attackers can access functionality not properly constrained by access control lists (ACLs) through a user-controlled key mechanism.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 is installedIn WordPress admin, go to Plugins > Installed Plugins and look for LearnPress, or check the /wp-content/plugins directory for the learnpress folderAffected if LearnPress plugin is present in the WordPress installation
-
Check installed LearnPress versionIn WordPress admin, go to Plugins > Installed Plugins and find the LearnPress version number displayed below the plugin name, or check the version in learnpress/readme.txt or learnpress/learnpress.php headerAffected if Version is 4.2.6.8.2 or lower
-
Identify user-controlled key mechanism usageSearch WordPress codebase for hooks or functions handling user-supplied keys in LearnPress (look for $_GET, $_POST, or $_REQUEST parameters used as keys in access control logic, particularly in LP_Auth or similar classes)Affected if Custom key or token parameters are accepted from user input without proper ACL validation
-
Review ACL configuration for LearnPress endpointsExamine WordPress user roles and LearnPress capability settings under LearnPress > Settings > Advanced, and check if any public-facing endpoints bypass normal WordPress capability checksAffected if LearnPress endpoints are accessible to unauthenticated or lower-privileged users without proper capability verification
-
Check for suspicious API activity in access logsReview web server access logs (Apache/Nginx) for repeated requests to LearnPress AJAX or REST endpoints with unusual key or token parameters, particularly from non-admin IP addressesAffected if Requests to LearnPress endpoints include user-supplied key parameters and return successful responses for privileged operations
User is affected if LearnPress version is 4.2.6.8.2 or lower AND the plugin is active with endpoints accepting user-controlled keys without proper authorization checks.
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 dataUpdate LearnPress to the vendor's latest patched version immediately to remediate the authorization bypass; verify ACL constraints function correctly after the update.
- 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-39642 — 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-39642 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