Contact Form Builder by vcita <= 4.10.3 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 4.10.5
- Affected Plugin
- Contact Form Builder by vcita
- Affected Version
<= 4.10.3- CVSS
- 6.1Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-2301
At a glance
CVE-2023-2301 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Contact Form Builder by vcita WordPress plugin, affecting versions <= 4.10.3. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.10.5; sites on affected versions should update now. Disclosed June 2023, reported by Jonas Höbenreich.
Vulnerability Overview
The Contact Form Builder by vcita plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.10.3. This is due to missing nonce validation on the ls_parse_vcita_callback function. This makes it possible for unauthenticated attackers to modify the plugin's settings and inject malicious JavaScript via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. While the Cross-Site Scripting issue was patched in version 4.10.1, the plugin is still technically vulnerable to Cross-Site Request Forgery since a capability check but no nonce check was added in 4.10.2.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Contact Form Builder by vcita <= 4.10.3 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 Contact Form Builder by vcita the fix is 4.10.5: builds <= 4.10.3 are affected, anything from 4.10.5 onward is not.
Remediation
Update to version 4.10.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Contact Form Builder by vcita: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Contact Form Builder by vcita 4.10.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