WordPress security by component
Contact Form Builder
Plugin description
Contact Form Builder is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published May 10, 2026; the highest published CVSS base score is 7.1.
Plugin slug:
contact-forms-builderLatest vulnerability
CVE-2022-50959: Contact Form Builder: Cross-site scripting
Contact Form Builder is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is 1.6.1. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| May 10, 2026 |
CVE-2022-50959
Contact Form Builder: Cross-site scripting
Contact Form Builder is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is 1.6.1. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.1
NVDPending
|
| Jun 10, 2024 |
CVE-2024-35747
Contact Form Builder, Contact Widget: A security weakness
Contact Form Builder, Contact Widget is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE5.3
NVD5.3
|
| Oct 26, 2023 |
CVE-2023-46075
Contact Forms Builder: Cross-site scripting
Contact Forms Builder is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE7.1
NVD6.1
|