dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-37438

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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 Pro for LearnDash allows Cross Site Request Forgery.This issue affects Uncanny Toolkit Pro for LearnDash: from n/a before 4.1.4.1.

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 Pro for LearnDash WordPress plugin allows attackers to trick authenticated users into performing unintended actions via malicious requests. The vulnerability exists in versions prior to 4.1.4.1, likely due to missing or improper anti-CSRF token validation on state-changing forms and actions.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions that modify data, and verify the nonce validity server-side before processing any state-changing requests.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

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 plugin is installed
    Check your WordPress plugins directory or wp-admin/plugins.php for 'Uncanny Toolkit Pro for LearnDash' or 'uncanny-toolkit-pro'
    Affected if Plugin is not installed means not affected
  2. Check installed version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number of Uncanny Toolkit Pro for LearnDash
    Affected if Version is present and less than 4.1.4.1 (e.g., 4.1.4, 4.1.3, 4.0.x, etc.)
  3. Identify state-changing forms and AJAX actions
    Review plugin files for form submissions and AJAX handlers that modify data (look for $_POST, $_GET, wp_ajax_ hooks, and admin-post.php handling)
    Affected if Forms or AJAX actions exist that do not verify WordPress nonces (look for missing wp_verify_nonce, check_admin_referer, or wp_nonce_field calls)
  4. Verify nonce validation on data-modifying endpoints
    Examine the server-side code for forms/AJAX actions that change data - check that each performs nonce verification before processing
    Affected if Any state-changing form or AJAX action lacks proper nonce validation (no call to wp_verify_nonce or check_admin_referer before processing)

You are affected if the Uncanny Toolkit Pro for LearnDash plugin is installed with a version prior to 4.1.4.1 AND contains forms or AJAX actions that modify data without verifying WordPress nonces.

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

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions that modify data, and verify the nonce validity server-side before processing any state-changing requests.

Recommended fix Moderate confidence

4.1.4.1 or later

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'Uncanny Toolkit Pro for LearnDash' in the plugin list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 4.1.4.1 or later.
  6. 6. Alternatively, download the latest version from the Uncanny Owl website or WordPress plugin repository and manually upload via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin is running version 4.1.4.1 or higher.
  8. 8. Test critical LearnDash functionality to ensure the update did not break existing features.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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