Crony Cronjob Manager < 0.4.7 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 0.4.7
- Affected Plugin
- Crony Cronjob Manager
- Affected Version
< 0.4.7- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2017-14530
At a glance
CVE-2017-14530 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Crony Cronjob Manager WordPress plugin, affecting versions < 0.4.7. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 0.4.7; sites on affected versions should update now. Disclosed October 2015, reported by Cyber Security Works Pvt. Ltd.
Vulnerability Overview
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.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Crony Cronjob Manager < 0.4.7 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Crony Cronjob Manager the fix is 0.4.7: builds < 0.4.7 are affected, anything from 0.4.7 onward is not.
Remediation
Update to version 0.4.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Crony Cronjob Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Crony Cronjob Manager 0.4.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C