dbcve.org
LearnpressWordPress extension · Thimpress

CVE-2023-6567

HIGH · 7.5 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to 4.2.5.8 or later.
See remediation →
84/100
Remediation priority · High
High EPSS 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 time-based SQL Injection via the ‘order_by’ parameter in all versions up to, and including, 4.2.5.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 time-based SQL injection vulnerability in the 'order_by' parameter. Due to insufficient escaping of user-supplied input and lack of prepared statements in the underlying SQL query, unauthenticated attackers can inject arbitrary SQL commands to extract sensitive data from the database.

MitigationUpdate LearnPress to version 4.2.5.8 or later to apply the patch that properly sanitizes the 'order_by' parameter and implements prepared statements. If immediate update is not possible, consider restricting access to the affected endpoint 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.5.8

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Verify LearnPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for LearnPress by Thimpress, or check the /wp-content/plugins/learnpress directory exists on the server
    Affected if The LearnPress plugin is found installed on the WordPress site
  2. Check installed LearnPress version
    Navigate to Plugins > Installed Plugins > LearnPress and note the version number, or read the version from the plugin's main PHP file header in /wp-content/plugins/learnpress/learnpress.php
    Affected if The installed version is below 4.2.5.8 (for example, 4.2.5.7, 4.2.5.6, etc.)
  3. Identify accessible endpoints using the order_by parameter
    Check WordPress routing for endpoints that process the 'order_by' parameter, typically found in LearnPress course listing or archive pages. Common patterns include query strings like ?order_by= or ?lp_listing=...&order_by= in URLs
    Affected if The site uses LearnPress shortcodes or templates that accept an 'order_by' parameter in HTTP requests
  4. Confirm the order_by parameter is reachable without authentication
    Test accessing LearnPress course archive pages with an 'order_by' parameter as an unauthenticated (logged-out) user, such as visiting a page with ?order_by=title in the URL
    Affected if The vulnerable parameter accepts user input without requiring authentication

You are affected if LearnPress is installed with a version lower than 4.2.5.8 and the order_by parameter is accessible on your site.

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.5.8 or later
Fixed in 4.2.5.8
Interim mitigation

Update LearnPress to version 4.2.5.8 or later to apply the patch that properly sanitizes the 'order_by' parameter and implements prepared statements. If immediate update is not possible, consider restricting access to the affected endpoint via web server configuration.

Recommended fix High confidence

LearnPress 4.2.5.8

  1. Backup your WordPress site and database before performing any updates
  2. Update the LearnPress plugin to version 4.2.5.8 or later through the WordPress admin dashboard (Plugins > Installed Plugins > LearnPress > Update Now)
  3. Alternatively, update via FTP by downloading LearnPress 4.2.5.8+ from wordpress.org/plugins/learnpress and uploading to wp-content/plugins/
  4. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
  5. Clear any site caches if a caching plugin is in use
  6. Test that LearnPress functionality (courses, orders, etc.) works correctly after the update

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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