PatchTheCVECVE-2017-14530: WP_Admin_UI in the Crony Cronjob Manager plugin before 0.4.7 for WordPress has CSRF via the name parameter in
CVE-2017-14530 is a high-severity flaw (CVSS 8.0) affecting crony cronjob manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
WP_Admin_UI in the Crony Cronjob Manager plugin before 0.4.7 for WordPress has CSRF via the name parameter in an action=manage&do=create operation, as demonstrated by inserting XSS sequences.
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.0 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | Required |
| EPSS exploit chance | 0.7% (top 48%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2017-09-18 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-14530?
crony cronjob manager: upgrade to newer than 0.4.6. Exact commands for each OS are on this page.
Is CVE-2017-14530 being exploited?
CVE-2017-14530 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2017-14530 affect?
CVE-2017-14530 affects crony cronjob manager. Severity is high (CVSS 8.0). WP_Admin_UI in the Crony Cronjob Manager plugin before 0.4.7 for WordPress has CSRF via the name parameter in an action=manage&do=create operation, as demonstrated by inserting XSS sequences.
How urgent is CVE-2017-14530?
Priority 46/100. High severity; Public exploit reference