dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-5207

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 LifterLMS plugin for WordPress is vulnerable to SQL Injection via the 'order' parameter in all versions up to, and including, 9.2.1. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Instructor-level access and above who have the edit_post capability on the quiz, 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

SQL injection vulnerability in LifterLMS WordPress plugin (versions up to 9.2.1) via the 'order' parameter. Insufficient input sanitization and lack of prepared statements in the SQL query allows authenticated users with Instructor-level access and edit_post capability on quizzes to inject arbitrary SQL commands.

MitigationUpgrade LifterLMS to version 9.2.2 or later. If immediate upgrade is not possible, restrict quiz editing permissions to admin-only until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 LifterLMS plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and confirm LifterLMS appears in the list. Alternatively, check /wp-content/plugins/lifterlms/ directory or query the wp_options table for 'lifterlms_version'
    Affected if LifterLMS plugin is not found in the WordPress installation
  2. Determine installed LifterLMS version
    Navigate to LifterLMS > Settings > About in the WordPress admin panel, or inspect the plugin header in /wp-content/plugins/lifterlms/lifterlms.php for the 'Version' field
    Affected if The version is 9.2.1 or lower (any version up to and including 9.2.1)
  3. Confirm quizzes functionality is active
    Check if the LifterLMS quiz module is enabled by reviewing the LifterLMS > Settings > General page, or attempt to access a quiz post type at /wp-admin/edit.php?post_type=llms_quiz
    Affected if Quiz post type exists and is accessible (the vulnerable parameter is used in quiz-related queries)
  4. Identify users with Instructor role and quiz edit capabilities
    In WordPress admin, go to Users > All Users and filter by 'Instructor' role, or query wp_usermeta for users with 'wp_capabilities' containing 'instructor' and 'edit_posts' capability for llms_quiz post type
    Affected if Any user account has Instructor role AND edit_post capability on quizzes, allowing them to trigger the 'order' parameter

You are affected if LifterLMS version 9.2.1 or lower is installed AND quizzes are accessible to users with Instructor-level edit_post permissions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade LifterLMS to version 9.2.2 or later. If immediate upgrade is not possible, restrict quiz editing permissions to admin-only until the patch can be applied.

Recommended fix High confidence

Upgrade to LifterLMS version 9.3.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the LifterLMS plugin
  4. Click 'Update Now' if an update is available, or manually upload the latest version from wordpress.org
  5. Verify the update completed successfully
  6. Clear any caching layers if applicable

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

Have this fixed 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 help mitigating

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-2026-5207 — 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-2026-5207 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