dbcve.org
LearnpressWordPress extension · Thimpress

CVE-2024-5483

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-05
Fix available
A fix is available. Upgrade to 4.2.6.8.1 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The LearnPress – WordPress LMS Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.2.6.8 due to incorrect implementation of get_items_permissions_check function. This makes it possible for unauthenticated attackers to extract basic information about website users, including their emails

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 has a broken access control vulnerability in its get_items_permissions_check function. This function incorrectly validates permissions, allowing unauthenticated attackers to bypass authentication and query user data including email addresses through the plugin's API endpoints.

MitigationUpdate LearnPress plugin to version 4.2.6.9 or later where the get_items_permissions_check function properly validates user permissions. If immediate update is not possible, consider restricting access to the affected API endpoints via web server configuration.

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.8.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Check installed LearnPress version
    In WordPress admin, go to Plugins > Installed Plugins > LearnPress, or check the version in the plugin's main PHP file (typically in wp-content/plugins/learnpress/ folder, look for version defined in the plugin header or main class)
    Affected if Version is lower than 4.2.6.8.1 or version cannot be determined (plugin may be outdated or from unverified source)
  2. Verify LearnPress plugin is active
    In WordPress admin, navigate to Plugins > Installed Plugins and confirm LearnPress status shows as 'Active', or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' LIKE '%learnpress%'
    Affected if Plugin is installed but inactive - vulnerability cannot be exploited; however, if plugin is active, proceed to next check
  3. Identify exposed API endpoints
    Check for LearnPress REST API routes by accessing /wp-json/lp/v1/ or /wp-json/learnpress/v1/ endpoints, or inspect the plugin's inc/rest-api directory for registered endpoints that use get_items_permissions_check
    Affected if API endpoints are publicly accessible without authentication - this confirms the attack surface exists
  4. Test unauthenticated user data access
    Send a GET request to LearnPress API endpoints that return user data (such as /wp-json/lp/v1/users or similar endpoint) without providing authentication credentials - examine if email addresses or other PII are returned in the response
    Affected if Unauthenticated requests return user data including email addresses - this confirms the vulnerability is exploitable in the environment

Environment is affected if LearnPress plugin version is below 4.2.6.8.1, the plugin is active, and unauthenticated API requests can retrieve user email addresses or other sensitive data.

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.8.1 or later
Fixed in 4.2.6.8.1
Interim mitigation

Update LearnPress plugin to version 4.2.6.9 or later where the get_items_permissions_check function properly validates user permissions. If immediate update is not possible, consider restricting access to the affected API endpoints via web server configuration.

Recommended fix High confidence

4.2.6.8.1

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find the LearnPress (LearnPress – WordPress LMS Plugin) plugin
  4. Click 'Update Now' if an update is available, or manually upload version 4.2.6.8.1 from the WordPress plugin repository
  5. Verify the update completed successfully by checking the plugin version number
  6. Confirm the vulnerability is resolved by testing that unauthenticated users can no longer access user email information

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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