Contact Builder by Themify <= 1.4.5 - Email Injection
Strategic Overview
- Status
- Patched in 1.4.6
- Affected Plugin
- Contact Builder by Themify
- Affected Version
<= 1.4.5- CVSS
- 5.3Medium
- Weakness type
- CWE-20 · Improper Input Validation
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Input Validation vulnerability in the Contact Builder by Themify WordPress plugin, affecting versions <= 1.4.5. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.4.6; sites on affected versions should update now. Disclosed July 2020, reported by David Cucala.
Vulnerability Overview
The Contact Builder by Themify plugin is vulnerable to email injection in versions up to, and including 1.4.5. This makes it possible for attackers to forward contact form submissions as a "copy" to the contact-email supplied even when the setting is disabled. In addition, the contact-message does not do any input sanitization allowing HTML to be injected into the message content. This was being actively exploited to craft phishing emails and sending those via the vulnerable sites.
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.
CWE-20: Improper Input Validation
Contact Builder by Themify <= 1.4.5 carries this weakness at copy, and reaching it takes a caller who can reach the endpoint. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.
The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For Contact Builder by Themify the fix is 1.4.6: builds <= 1.4.5 are affected, anything from 1.4.6 onward is not.
Remediation
Update to version 1.4.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Contact Builder by Themify: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Contact Builder by Themify 1.4.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C