Get URL Cron <= 1.4.7 - Missing Authorization via geturlcron_action_handle
Strategic Overview
- Status
- Patched in 1.4.8
- Affected Plugin
- Cron Setup and Monitor – Get URL Cron
- Affected Version
<= 1.4.7- CVSS
- 7.5High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Missing Authorization vulnerability in the Cron Setup and Monitor WordPress plugin, affecting versions <= 1.4.7. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.4.8; sites on affected versions should update now. Disclosed February 2023, reported by Rio Darmawan.
Vulnerability Overview
The Get URL Cron plugin for WordPress is vulnerable to unauthorized modification of data in versions up to, and including, 1.4.7. This is due to a missing capability check on the geturlcron_action_handle function called via an init hook. This makes it possible for unauthenticated attackers to modify many of the plugin's settings, retrieve cron jobs, and create cron jobs.
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. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Reaching this weakness in Cron Setup and Monitor <= 1.4.7 takes a caller who can reach the endpoint. 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 Cron Setup and Monitor the fix is 1.4.8: builds <= 1.4.7 are affected, anything from 1.4.8 onward is not.
Remediation
Update to version 1.4.8, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Cron Setup and Monitor 1.4.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Cron Setup and Monitor – Get URL Cron
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C