Uncanny Automator Pro < 5.3.0.1 - Missing Authorization to Unauthenticated License Setting Reset
Strategic Overview
- Status
- Patched in 5.3.0.1
- Affected Plugin
- Uncanny Automator Pro
- Affected Version
< 5.3.0.1- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-37119
At a glance
CVE-2024-37119 is a medium-severity Missing Authorization vulnerability in the Uncanny Automator Pro WordPress plugin, affecting versions < 5.3.0.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.3.0.1; sites on affected versions should update now. Disclosed June 2024, reported by Dave Jong.
Vulnerability Overview
The Uncanny Automator Pro plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on a function in all versions up to 5.3.0.1 (exclusive). This makes it possible for unauthenticated attackers to reset the plugin's license settings.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Uncanny Automator Pro < 5.3.0.1 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Uncanny Automator Pro the fix is 5.3.0.1: builds < 5.3.0.1 are affected, anything from 5.3.0.1 onward is not.
Remediation
Update to version 5.3.0.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Uncanny Automator Pro 5.3.0.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Uncanny Automator Pro
- 9.8CVE-2026-12375: Uncanny Automator Pro… Maliciously Injected Backdoor
CVE-2026-12375 - 7.5CVE-2026-56057: Uncanny Automator Pro <= 7.3.0.6 PHP Object Injection
CVE-2026-56057 - 6.1CVE-2024-37117: Uncanny Automator Pro <= 5.3 Reflected XSS
CVE-2024-37117 - 4.3CVE-2024-37118: Uncanny Automator Pro CSRF to License Setting Reset
CVE-2024-37118
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C