dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-2446

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The PowerPack for LearnDash WordPress plugin before 1.3.0 does not have authorization and CRSF checks in an AJAX action, allowing unauthenticated users to update arbitrary WordPress options (such as default_role etc) and create arbitrary admin users

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 PowerPack for LearnDash WordPress plugin before 1.3.0 contains a vulnerable AJAX action that lacks both authorization checks and CSRF protection, enabling unauthenticated attackers to modify arbitrary WordPress options and create administrator-level user accounts.

MitigationImmediately update the PowerPack for LearnDash plugin to version 1.3.0 or later; if the site shows signs of compromise (unknown admin accounts, modified options), conduct a forensic review and remove any unauthorized users.

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
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 PowerPack for LearnDash is installed
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, and locate the PowerPack for LearnDash plugin. Alternatively, check if the /wp-content/plugins/powerpack-learndash/ directory exists on the server.
    Affected if The plugin is present on the WordPress site
  2. Check installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, find PowerPack for LearnDash and compare the version number displayed against version 1.3.0. Any version lower than 1.3.0 is affected.
    Affected if The installed version is lower than 1.3.0
  3. Inspect for unauthorized administrator accounts
    Navigate to Users > All Users in the WordPress admin panel and review the list for any unknown accounts with the Administrator role, or query the wp_users and wp_usermeta database tables directly for user_capabilities showing administrator privileges that were not created by site administrators.
    Affected if Unexpected administrator accounts exist that were not created by legitimate site admins
  4. Review WordPress options for unauthorized changes
    Check WordPress options table (wp_options) for modifications to siteurl, home, or other critical settings that were not made by administrators. Also look for new Transients or options containing suspicious values.
    Affected if Critical WordPress options have been modified without legitimate administrator action

The environment is affected if PowerPack for LearnDash plugin version is below 1.3.0 and the site shows signs of unauthorized admin account creation or option modifications.

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

Immediately update the PowerPack for LearnDash plugin to version 1.3.0 or later; if the site shows signs of compromise (unknown admin accounts, modified options), conduct a forensic review and remove any unauthorized users.

Recommended fix Moderate confidence

PowerPack for LearnDash version 1.3.0 or later

  1. Log into the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'PowerPack for LearnDash' in the plugin list
  4. Check the current version number - if below 1.3.0, an update is needed
  5. If an update is available, click 'Update Now' to install version 1.3.0 or later
  6. After updating, verify the new version number is 1.3.0 or higher
  7. Review user accounts in Users > All Users to confirm no unauthorized admin accounts were created
  8. Check WordPress settings (particularly in Settings > General) for any unauthorized changes to options like default_role

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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