dbcve.org
Uncanny Toolkit For LearndashWordPress extension · Uncannyowl

CVE-2023-23714

HIGH · 8.8 CVSS v3.1 Published 2023-05-26
Fix available
A fix is available. Upgrade to after 3.6.4.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Uncanny Owl Uncanny Toolkit for LearnDash plugin <= 3.6.4.1 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Uncanny Owl Uncanny Toolkit for LearnDash WordPress plugin versions 3.6.4.1 and earlier. The plugin lacks proper CSRF token validation on certain actions, allowing attackers to trick authenticated administrators into performing unintended operations such as modifying plugin settings or user data.

MitigationUpdate to the latest version of the Uncanny Toolkit for LearnDash plugin (vendor should have released a patch). Additionally, implement anti-CSRF tokens (nonces) on all state-changing form submissions and validate the Referer header.

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
Uncanny Toolkit For LearndashWordPress extension
Affected:<= 3.6.4.1

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Uncanny Owl Uncanny Toolkit for LearnDash' in the list of active plugins.
    Affected if The plugin appears in the list of installed plugins.
  2. Check installed version number
    In the Plugins list, locate the Uncanny Toolkit for LearnDash plugin and note the version number displayed below the plugin name. Alternatively, check the plugin header in the main plugin file (typically in wp-content/plugins/uncanny-toolkit-for-learndash/).
    Affected if A version number is displayed and matches <= 3.6.4.1.
  3. Compare version to affected range
    Compare your installed version against the affected range: versions 3.6.4.1 and earlier. Any version at or below 3.6.4.1 is vulnerable.
    Affected if Installed version is 3.6.4.1 or lower.
  4. Identify unprotected admin actions
    Review plugin source code for admin action handlers (typically in includes/ or src/ directories). Search for action hooks handling state-changing requests (POST/GET requests that modify settings or user data) and verify whether each handler includes nonce verification using functions like wp_verify_nonce(), check_admin_referer(), orwp_nonce_field().
    Affected if Admin action handlers lack nonce/token validation before processing requests.

A user is affected if the Uncanny Toolkit for LearnDash plugin is installed with version 3.6.4.1 or earlier and lacks proper CSRF token validation on administrative actions.

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 a release after 3.6.4.1
Interim mitigation

Update to the latest version of the Uncanny Toolkit for LearnDash plugin (vendor should have released a patch). Additionally, implement anti-CSRF tokens (nonces) on all state-changing form submissions and validate the Referer header.

Recommended fix Moderate confidence

Version 3.6.5 or later (update to latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Uncanny Toolkit for LearnDash' and click 'Update Now'
  4. Verify the updated version number is displayed after updating
  5. Confirm the update was successful by checking the plugins page
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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

Fix this in Uncanny Toolkit For Learndash Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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