WDContactFormBuilder <= 1.0.68 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 1.0.69
- Affected Plugin
- WDContactFormBuilder
- Affected Version
< 1.0.69- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2019-11557
At a glance
CVE-2019-11557 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WDContactFormBuilder WordPress plugin, affecting versions < 1.0.69. 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 1.0.69; sites on affected versions should update now. Disclosed April 2019, reported by Panagiotis Vagenas.
Vulnerability Overview
The WebDorado Contact Form Builder plugin before 1.0.69 for WordPress allows CSRF via the wp-admin/admin-ajax.php action parameter, with resultant local file inclusion via directory traversal, because there can be a discrepancy between the $_POST['action'] value and the $_GET['action'] value, and the latter is unsanitized.
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)
WDContactFormBuilder < 1.0.69 carries this weakness at action, and reaching it 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 WDContactFormBuilder the fix is 1.0.69: builds < 1.0.69 are affected, anything from 1.0.69 onward is not.
Remediation
Update to version 1.0.69, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WDContactFormBuilder: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WDContactFormBuilder 1.0.69 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WDContactFormBuilder
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C