HandL UTM Grabber / Tracker <= 2.6.4 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.6.5
- Affected Plugin
- HandL UTM Grabber / Tracker
- Affected Version
< 2.6.5- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2019-15769
At a glance
CVE-2019-15769 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the HandL UTM Grabber / Tracker WordPress plugin, affecting versions < 2.6.5. 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 2.6.5; sites on affected versions should update now. Disclosed August 2019.
Vulnerability Overview
The handl-utm-grabber plugin before 2.6.5 for WordPress has CSRF via add_option and update_option.
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 HandL UTM Grabber / Tracker < 2.6.5 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 HandL UTM Grabber / Tracker the fix is 2.6.5: builds < 2.6.5 are affected, anything from 2.6.5 onward is not.
Remediation
Update to version 2.6.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to HandL UTM Grabber / Tracker: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: HandL UTM Grabber / Tracker 2.6.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C