dbcve.org
LifterlmsWordPress extension

CVE-2025-52717

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-27
Fix available
A fix is available. Upgrade to 8.0.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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in chrisbadgett LifterLMS lifterlms allows SQL Injection.This issue affects LifterLMS: from n/a through <= 8.0.6.

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

A critical SQL Injection vulnerability exists in the LifterLMS WordPress plugin. The vulnerability allows attackers to inject malicious SQL commands through unsanitized input, potentially enabling unauthorized data access, modification, or deletion of database contents. The CVSS score of 9.8 indicates this is remotely exploitable without authentication and can completely compromise confidentiality, integrity, and availability.

MitigationUpgrade LifterLMS to version 8.0.7 or later, which contains the patched code addressing the SQL injection vulnerability. Before upgrading, ensure a full backup is taken and test the upgrade in a staging environment to verify compatibility with other installed plugins and themes.

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
LifterlmsWordPress extension
Affected:< 8.0.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 LifterLMS is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for LifterLMS in the list. Alternatively, check the file system at wp-content/plugins/lifterlms/ for the plugin directory.
    Affected if The LifterLMS plugin directory exists in the WordPress installation.
  2. Confirm LifterLMS is active
    In the WordPress admin under Plugins > Installed Plugins, verify the LifterLMS plugin shows as 'Active'. SQL injection requires the plugin to be loaded and processing user input.
    Affected if The LifterLMS plugin is currently activated on the WordPress site.
  3. Find the installed LifterLMS version
    In WordPress admin, go to Plugins > Installed Plugins and click on the LifterLMS plugin to view its details, which displays the version number. Alternatively, check the plugin header in wp-content/plugins/lifterlms/lifterlms.php or the readme.txt file for the Version field.
    Affected if A specific version number is returned from the plugin files or WordPress.
  4. Compare version against affected range
    Take the version number found in the previous step and compare it to 8.0.7. Any version less than 8.0.7 (for example: 8.0.6, 8.0.0, 7.8.1, etc.) falls within the affected range.
    Affected if The installed version is lower than 8.0.7 (for example: 8.0.6, 7.8.0, 7.7.2, etc.).

The site is affected if LifterLMS is installed, active, and running a version lower than 8.0.7.

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 8.0.7 or later
Fixed in 8.0.7
Interim mitigation

Upgrade LifterLMS to version 8.0.7 or later, which contains the patched code addressing the SQL injection vulnerability. Before upgrading, ensure a full backup is taken and test the upgrade in a staging environment to verify compatibility with other installed plugins and themes.

Recommended fix High confidence

LifterLMS 8.0.7

  1. Create a complete backup of your WordPress database and files.
  2. Update LifterLMS to version 8.0.7 or later. This can be done via the WordPress Admin Dashboard under 'Dashboard > Updates', or via WP-CLI using the command 'wp plugin update lifterlms'.
  3. Verify the update was successful by checking the installed plugins version.
  4. Test critical LifterLMS functionalities (e.g., course enrollment, quiz submissions) to ensure the update did not introduce any regressions.

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

Fix this in Lifterlms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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