dbcve.org
LearnpressWordPress extension · Thimpress

CVE-2023-36515

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-19
Fix available
A fix is available. Upgrade to 4.2.3.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Missing Authorization vulnerability in ThimPress LearnPress.This issue affects LearnPress: from n/a through 4.2.3.

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 confidence

LearnPress WordPress plugin versions through 4.2.3 contain a missing authorization vulnerability that allows unauthenticated or unauthorized users to access sensitive functionality or perform actions beyond their privilege level. This critical severity flaw (CVSS 9.8) likely involves REST API endpoints or AJAX actions lacking proper capability checks or permission_callback validations.

MitigationUpdate LearnPress to the latest version immediately. If no patch is available, audit REST API endpoints and AJAX actions to add proper permission_callback checks and capability verification before allowing any administrative or privileged operations.

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.3.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'LearnPress' or check the version in the plugin file header at wp-content/plugins/learnpress/readme.txt or wp-content/plugins/learnpress/learnpress.php
    Affected if LearnPress plugin is present on the site
  2. Determine installed LearnPress version
    Check the version number in the plugin header of learnpress.php or in the readme.txt file, or query the WordPress plugins API endpoint /wp-json/wp/v2/plugins?search=learnpress
    Affected if Version is less than 4.2.3.1 (e.g., 4.2.3, 4.2.2, etc.)
  3. Identify exposed REST API endpoints
    Access the WordPress REST API at /wp-json/ and look for LearnPress-related routes (typically under /wp-json/lp/v1/ or /wp-json/learnpress/v1/), then test these endpoints without providing authentication credentials
    Affected if LearnPress REST API endpoints respond without requiring authentication and return sensitive data or allow privileged actions
  4. Test AJAX actions for missing authorization
    Inspect the plugin's JavaScript files for AJAX calls (wp.ajax) and test the corresponding admin-ajax.php actions with unauthenticated requests, checking if they execute privileged operations
    Affected if AJAX actions related to LearnPress execute or return privileged data without verifying user capabilities
  5. Verify permission_callback checks on REST routes
    Examine the plugin's rest-api.php or similar files to confirm that REST route registrations include permission_callback functions that validate user capabilities
    Affected if REST API routes lack permission_callback validation or use permissive callbacks that allow any user

You are affected if LearnPress version is below 4.2.3.1 AND the REST API or AJAX endpoints are accessible to unauthenticated users without proper capability verification.

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.3.1 or later
Fixed in 4.2.3.1
Interim mitigation

Update LearnPress to the latest version immediately. If no patch is available, audit REST API endpoints and AJAX actions to add proper permission_callback checks and capability verification before allowing any administrative or privileged operations.

Recommended fix Moderate confidence

4.2.3.1

  1. Backup your WordPress site and database before updating
  2. Update LearnPress plugin to version 4.2.3.1 through the WordPress admin dashboard (Plugins > Updates) or via wp-cli: wp plugin update learnpress
  3. Verify the update completed successfully
  4. Test that LearnPress functionality works as expected
  5. Clear any caching if applicable

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

Fix this in Learnpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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