dbcve.org
Uncanny AutomatorWordPress extension · Uncannyowl

CVE-2024-37118

HIGH · 8.8 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to after 5.3 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 Automator Pro.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

Cross-Site Request Forgery (CSRF) vulnerability in Uncanny Automator Pro plugin allows attackers to trick authenticated administrators into executing unintended actions, such as triggering automated workflows or modifying plugin settings, by forcing their browser to send malicious requests.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing operations, validate Origin/Referer headers on POST requests, and set SameSite attribute on session cookies.

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

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. Check if Uncanny Automator Pro is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Uncanny Automator Pro' or 'Uncanny Automator' in the list of active plugins
    Affected if The plugin is not found in the installed plugins list
  2. Identify the installed version number
    In the Plugins list page, locate the Uncanny Automator entry. Click on the plugin name or hover over it to reveal the version number displayed beneath the plugin title, or check the plugin's main PHP file (typically uncanny-automator-pro.php or similar in wp-content/plugins/ directory) for the 'Version' header in the file comment block
    Affected if Version cannot be determined or is not visible
  3. Compare version to affected range
    Compare the installed version number to the affected range: any version 5.3 or lower (e.g., 5.3, 5.2.1, 5.2, 5.1, 5.0, etc.) is within the affected range
    Affected if Installed version is 5.3 or lower (e.g., 5.2, 5.1, 5.0)
  4. Verify the plugin is active on the site
    In WordPress admin > Plugins > Installed Plugins, confirm the plugin shows as 'Active' rather than 'Inactive' or 'Must Use'
    Affected if Plugin is active and version is 5.3 or lower

User is affected if Uncanny Automator Pro plugin is installed, active, and running version 5.3 or lower.

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 5.3
Interim mitigation

Implement anti-CSRF tokens (nonces) for all state-changing operations, validate Origin/Referer headers on POST requests, and set SameSite attribute on session cookies.

Recommended fix Moderate confidence

Uncanny Automator Pro version 5.4 or later

  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 an update is available (compare current version to the latest version)
  5. If an update is available, click 'Update Now' to update to the latest version (5.4 or later)
  6. Alternatively, download the latest version from the WordPress repository or from Uncanny Owl's official website
  7. Deactivate and delete the old version if automatic update does not work, then upload and activate the new version
  8. Verify the update was successful by checking the plugin version number
Caveat Review the plugin's changelog for any breaking changes before updating in production environments

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
  • 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-2024-37118 — 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-37118 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