dbcve.org
Uncanny AutomatorWordPress extension · Uncannyowl

CVE-2024-37117

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 5.3.0.1 or later.
See remediation →
68/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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Uncanny Owl Uncanny Automator Pro allows Reflected XSS.This issue affects Uncanny Automator Pro: from n/a through 5.3.

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

Reflected XSS vulnerability in Uncanny Automator Pro allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in web pages without proper output encoding, enabling session hijacking or credential theft.

MitigationUpdate to a patched version of Uncanny Automator Pro that properly sanitizes and encodes all user-supplied input before rendering in web pages, or apply vendor-supplied security patch.

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

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

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 Uncanny Automator plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the 'uncanny-automator' folder, or run 'wp plugin list --search="uncanny automator"' via WP-CLI if available
    Affected if The plugin folder 'uncanny-automator' exists in the WordPress plugins directory
  2. Check the installed version number
    Open the main plugin file (typically uncanny-automator/uncanny-automator.php) and locate the 'Version:' header in the plugin comments, or use WordPress admin under Plugins > Installed Plugins
    Affected if The version displayed is less than 5.3.0.1 (for example, 5.3.0, 5.2.x, or earlier versions)
  3. Confirm the plugin is active
    Log into WordPress admin and check if Uncanny Automator appears in the list of active plugins, or run 'wp plugin status uncanny-automator' via WP-CLI
    Affected if The plugin shows as active or 'Enabled' in WordPress
  4. Identify reflected input points (optional for deeper analysis)
    Review the plugin settings pages and any public-facing forms or URLs that accept user input and may reflect it back in the response without encoding
    Affected if Any GET or POST parameters are reflected in the page output without proper sanitization (requires code review or manual testing)

You are affected if Uncanny Automator Pro is installed, active, and running a version lower than 5.3.0.1, as this version range contains the unsanitized user input reflection vulnerability.

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 a patched version of Uncanny Automator Pro that properly sanitizes and encodes all user-supplied input before rendering in web pages, or apply vendor-supplied security patch.

Recommended fix High confidence

5.3.0.1

  1. 1. Backup your WordPress site database and files before proceeding with any updates.
  2. 2. Log in to your WordPress admin dashboard.
  3. 3. Navigate to Plugins > Installed Plugins.
  4. 4. Locate 'Uncanny Automator Pro' in the plugin list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 5.3.0.1.
  6. 6. Alternatively, you can download the latest version (5.3.0.1) from your Uncanny Owl account and upload it manually via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin version shows 5.3.0.1 or higher.
  8. 8. Test critical workflows to ensure the Automator functionality works correctly after the update.
Caveat Review plugin changelog for any workflow compatibility changes; major version updates may require reconfiguration of existing recipes

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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