dbcve.org
Uncanny AutomatorWordPress extension · Uncannyowl

CVE-2024-37119

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 5.3.0.1 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
Missing Authorization vulnerability in Uncanny Owl Uncanny Automator Pro allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Uncanny Automator Pro: from n/a through 5.3.0.0.

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

A missing authorization vulnerability exists in Uncanny Automator Pro where the plugin fails to properly enforce access control checks, allowing attackers to exploit incorrectly configured security levels. The CVSS 9.8 score indicates this can likely be exploited remotely without authentication, potentially allowing unauthorized users to execute actions they should not have permission to perform.

MitigationUpdate to the patched version of Uncanny Automator Pro (beyond 5.3.0.0) and audit all automation recipes and user role permissions to ensure proper authorization controls are in place.

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 AutomatorWordPress extension
Affected:< 5.3.0.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
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 the installed version of Uncanny Automator
    Check the WordPress plugin directory or inspect the main plugin file header for the version number. In WordPress admin, go to Plugins > Installed Plugins and look for Uncanny Automator Pro or Uncannyowl Uncanny Automator.
    Affected if The installed version is less than 5.3.0.1 (for example, 5.3.0.0 or earlier).
  2. Confirm the plugin is active and accessible
    Verify the plugin is activated on the WordPress site. Check if the automation recipes functionality is publicly accessible or if the site allows guest/-logged-out users to trigger recipes.
    Affected if The plugin is active and automation recipes can be triggered without authentication or by users lacking proper authorization.
  3. Inspect automation recipe configurations
    Review all automation recipes in the WordPress dashboard under Automator > Recipes. Look for recipes that execute privileged actions (like creating users, modifying content, or sending emails) and check their trigger settings.
    Affected if Recipes with sensitive actions are configured to be triggerable by unauthenticated users or users without proper role permissions.
  4. Check for exposed automation endpoints
    Examine the site's REST API endpoints or any custom AJAX handlers exposed by the plugin. Look for unauthenticated endpoints under /wp-json/automator/ or similar paths.
    Affected if The plugin exposes endpoints that accept requests without requiring authentication or valid authorization tokens.

You are affected if the installed Uncanny Automator version is below 5.3.0.1 AND the site configuration allows unauthenticated or unauthorized users to trigger automation recipes.

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

Update to the patched version of Uncanny Automator Pro (beyond 5.3.0.0) and audit all automation recipes and user role permissions to ensure proper authorization controls are in place.

Recommended fix High confidence

Uncanny Automator Pro version 5.3.0.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Uncanny Automator Pro' in the plugin list
  4. Check if the current version is below 5.3.0.1
  5. If an update is available, click 'Update Now' to install version 5.3.0.1 or later
  6. Alternatively, navigate to Dashboard > Updates and select Uncanny Automator Pro for update
  7. After updating, verify the installed version is 5.3.0.1 or higher under Plugins > Installed Plugins

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

Fix this in Uncanny Automator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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