dbcve.org
Uncanny AutomatorWordPress extension · Uncannyowl

CVE-2025-48133

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-05
Fix available
A fix is available. Upgrade to 6.5.0 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 uncanny-automator allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Uncanny Automator: from n/a through <= 6.4.0.2.

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

Uncanny Automator WordPress plugin versions through 6.4.0.2 contain a Missing Authorization vulnerability (CWE-862) that allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized actions within the WordPress environment without proper authentication or privilege validation.

MitigationUpdate Uncanny Automator to the latest version (beyond 6.4.0.2) to patch the missing authorization check. Review user roles and permissions in WordPress until the patch is applied.

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:< 6.5.0

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. Confirm Uncanny Automator plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/uncanny-automator/ directory via file manager or FTP
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the Uncanny Automator entry - the version number is displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/uncanny-automator/uncanny-automator.php for the 'Version' tag
    Affected if The version displayed is any version prior to 6.5.0 (e.g., 6.4.0.2, 6.4.0, 6.3.x, etc.)
  3. Verify the plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm the plugin shows as 'Active' under the status column, or query the WordPress options table for the active_plugins option
    Affected if The plugin is active and running
  4. Check for publicly accessible Automator triggers
    Review Automator recipe configurations via WordPress admin > Automator > All Recipes. Look for recipes with triggers set to run on frontend events (such as user registration forms, comment submissions, or public form submissions) that do not require admin authentication
    Affected if Recipes exist that accept input from unauthenticated users or public-facing forms
  5. Inspect WordPress user roles and permissions
    Navigate to WordPress admin > Users > Roles and Permissions, or use a role management plugin to review what capabilities are assigned to subscriber, contributor, and other low-privilege roles, particularly any Automator-related capabilities
    Affected if Lower-privileged users (subscribers, guests) have capabilities that could allow triggering automated actions without proper authorization checks

Your environment is affected if Uncanny Automator version 6.5.0 or later is NOT installed AND the plugin is active with recipes accessible to unauthenticated or low-privilege users.

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

Update Uncanny Automator to the latest version (beyond 6.4.0.2) to patch the missing authorization check. Review user roles and permissions in WordPress until the patch is applied.

Recommended fix High confidence

Uncanny Automator version 6.5.0

  1. Backup your WordPress site database and files before proceeding
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Locate Uncanny Automator plugin and click 'Update now' or download version 6.5.0 from the WordPress plugin repository
  4. After update, verify the plugin version shows 6.5.0
  5. Test critical automated workflows to ensure functionality remains intact

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

Fix this in Uncanny Automator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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