dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3079

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-24
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 LearnDash LMS plugin for WordPress is vulnerable to blind time-based SQL Injection via the 'filters[orderby_order]' parameter in the 'learndash_propanel_template' AJAX action in all versions up to, and including, 5.0.3. 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 Contributor-level access and above, 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 LearnDash LMS plugin for WordPress contains a blind time-based SQL injection vulnerability in the 'learndash_propanel_template' AJAX action. The vulnerability stems from insufficient escaping of the 'filters[orderby_order]' parameter combined with a lack of prepared statements in the underlying SQL query, allowing authenticated attackers with Contributor-level access or higher to inject arbitrary SQL queries.

MitigationUpgrade to a patched version of LearnDash LMS when available; otherwise, implement proper input validation, parameterized queries (prepared statements), and sufficient escaping on the 'filters[orderby_order]' parameter in the affected AJAX handler.

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. Confirm LearnDash LMS plugin is installed
    Check the WordPress plugin directory or inspect the plugin header in /wp-content/plugins/learndash-lms/learndash.php for the 'Version' defined constant
    Affected if The plugin is not installed, the vulnerability does not apply
  2. Identify installed LearnDash version
    Read the Version value from the plugin header file mentioned above; compare to any published affected version ranges from LearnDash security advisories
    Affected if The installed version falls within an affected range and the plugin is active
  3. Verify Contributor-level users exist
    In WordPress admin, go to Users > All Users and check for any users with the Contributor role (or higher roles like Author, Editor, Admin)
    Affected if No users with Contributor access exist, the authenticated attack vector cannot be exploited
  4. Confirm propanel functionality is enabled
    Check if the LearnDash ProPanel addon/plugin is active, or if the 'learndash_propanel_template' AJAX action is registered; look for wp_ajax_learndash_propanel_template hooks in the codebase
    Affected if The propanel component is not active, the specific vulnerable AJAX action may not be reachable
  5. Inspect the vulnerable parameter handling
    Locate the AJAX handler for 'learndash_propanel_template' in the plugin files and examine how 'filters[orderby_order]' is processed before being used in SQL queries; check for direct insertion into queries without prepare() calls
    Affected if The code directly uses the parameter in SQL without proper escaping or prepared statements, confirming the vulnerability is present

If LearnDash LMS is installed with an affected version, has active Contributor-level users, and has the propanel AJAX functionality enabled with unescaped 'filters[orderby_order]' usage in SQL, the environment is vulnerable to CVE-2026-3079.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of LearnDash LMS when available; otherwise, implement proper input validation, parameterized queries (prepared statements), and sufficient escaping on the 'filters[orderby_order]' parameter in the affected AJAX handler.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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