dbcve.org
LearnpressWordPress extension · Thimpress

CVE-2023-6634

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to after 4.2.5.7 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
The LearnPress plugin for WordPress is vulnerable to Command Injection in all versions up to, and including, 4.2.5.7 via the get_content function. This is due to the plugin making use of the call_user_func function with user input. This makes it possible for unauthenticated attackers to execute any public function with one parameter, which could result in remote code execution.

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 plugin versions up to 4.2.5.7 contain a command injection vulnerability in the get_content function. The flaw stems from unsafe use of PHP's call_user_func() with unsanitized user input, enabling unauthenticated attackers to execute arbitrary public class methods accepting a single parameter, leading to remote code execution.

MitigationUpdate LearnPress to version 4.2.5.8 or later immediately. As a stopgap, disable the plugin or deploy WAF rules to block requests targeting the vulnerable endpoint until patching is possible.

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

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
    Check if the LearnPress plugin directory exists at wp-content/plugins/learnpress/ or look for LearnPress in WordPress admin under Plugins
    Affected if LearnPress plugin is present in the WordPress installation
  2. Check installed LearnPress version
    Read the main plugin file (usually learnpress.php) header for 'Version:' or check in WordPress admin Plugins list
    Affected if Version is 4.2.5.7 or lower (any version up to and including 4.2.5.7)
  3. Confirm REST API endpoint accessibility
    Test if the LearnPress REST API responds at /wp-json/learnpress/v1/ or check if REST API is enabled in WordPress general settings
    Affected if WordPress REST API is enabled and LearnPress REST endpoints are accessible (default state)
  4. Identify vulnerable get_content function usage
    Inspect the LP_REST_Controller class file in includes/rest-api/ directory for the get_content function using call_user_func()
    Affected if The get_content function exists and processes user input through call_user_func() without sanitization

If LearnPress version is 4.2.5.7 or lower and the plugin REST API is accessible, the environment is vulnerable to unauthenticated command injection via the get_content function.

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 a release after 4.2.5.7
Interim mitigation

Update LearnPress to version 4.2.5.8 or later immediately. As a stopgap, disable the plugin or deploy WAF rules to block requests targeting the vulnerable endpoint until patching is possible.

Recommended fix Moderate confidence

Latest LearnPress version available (greater than 4.2.5.7)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate LearnPress in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update is shown in WordPress, manually download the latest version from the official WordPress plugin repository at wordpress.org/plugins/learnpress/
  6. 6. Deactivate the current LearnPress plugin
  7. 7. Delete the current LearnPress plugin files
  8. 8. Upload and install the updated LearnPress plugin
Caveat Minor or major compatibility issues possible with WordPress core or other plugins; always test on staging environment first

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-2023-6634 — 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-6634 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