dbcve.org
LearndashWordPress extension

CVE-2020-6009

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-01
Fix available
A fix is available. Upgrade to 3.1.6 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
LearnDash Wordpress plugin version below 3.1.6 is vulnerable to Unauthenticated SQL Injection.

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

Unauthenticated SQL injection vulnerability in the LearnDash WordPress plugin affecting all versions prior to 3.1.6, allowing remote attackers to inject malicious SQL queries without any authentication credentials.

MitigationUpgrade LearnDash plugin to version 3.1.6 or later; if immediate upgrade is not possible, consider restricting access to the affected endpoints via web server configuration 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.

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
LearndashWordPress extension
Affected:< 3.1.6

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. Check LearnDash plugin version in WordPress admin
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate the LearnDash plugin entry and read the version number displayed below the plugin name.
    Affected if The displayed version is lower than 3.1.6 (for example, 3.1.5, 3.0.0, etc.)
  2. Check LearnDash version via wp-cli
    Run the command: wp plugin list --name=learndash --format=table in the WordPress root directory. The version column will show the installed version.
    Affected if The version listed is less than 3.1.6
  3. Verify LearnDash plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm that LearnDash shows as "Active" under the plugin status, or run: wp plugin list --name=learndash --status=active
    Affected if LearnDash is activated and the version is below 3.1.6
  4. Check plugin file header for version
    Inspect the main plugin file (typically /wp-content/plugins/sfwd-lms/sfwd_lms.php or similar) and look for the Version header in the plugin comment block.
    Affected if The Version header shows a number lower than 3.1.6

Your environment is affected if the LearnDash WordPress plugin is installed, active, and running at a version lower than 3.1.6.

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

Upgrade LearnDash plugin to version 3.1.6 or later; if immediate upgrade is not possible, consider restricting access to the affected endpoints via web server configuration until the patch can be applied.

Recommended fix High confidence

LearnDash 3.1.6

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the LearnDash plugin in the list
  4. Check the current version number to confirm it is below 3.1.6
  5. Click on Update Now if an update is available, or manually download LearnDash version 3.1.6 or higher from a trusted source
  6. If using automatic updates, ensure the plugin is configured to receive updates, or manually upload the new version via Plugins > Add New > Upload Plugin
  7. After updating, verify the new version number is 3.1.6 or higher
  8. Test critical LearnDash functionality (course enrollment, quiz submissions, reporting) to ensure the update did not break existing functionality
Caveat Review LearnDash 3.1.6 release notes for any feature changes or deprecations that may affect your site

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

Fix this in Learndash Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.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-2020-6009 — 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-2020-6009 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