Vulnerabilities (CVE)

Join the Common Vulnerabilities and Exposures (CVE) community and start to get notified about new vulnerabilities.

Filtered by vendor Strategy11 Subscribe
Filtered by product Formidable Form Builder
Total 4 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2023-24419 1 Strategy11 1 Formidable Form Builder 2023-03-09 N/A 8.8 HIGH
Cross-Site Request Forgery (CSRF) vulnerability in Strategy11 Form Builder Team Formidable Forms plugin <= 5.5.6 versions.
CVE-2021-24884 1 Strategy11 1 Formidable Form Builder 2022-08-30 6.8 MEDIUM 9.6 CRITICAL
The Formidable Form Builder WordPress plugin before 4.09.05 allows to inject certain HTML Tags like <audio>,<video>,<img>,<a> and<button>.This could allow an unauthenticated, remote attacker to exploit a HTML-injection byinjecting a malicous link. The HTML-injection may trick authenticated users to follow the link. If the Link gets clicked, Javascript code can be executed. The vulnerability is due to insufficient sanitization of the "data-frmverify" tag for links in the web-based entry inspection page of affected systems. A successful exploitation incomibantion with CSRF could allow the attacker to perform arbitrary actions on an affected system with the privileges of the user. These actions include stealing the users account by changing their password or allowing attackers to submit their own code through an authenticated user resulting in Remote Code Execution. If an authenticated user who is able to edit Wordpress PHP Code in any kind, clicks the malicious link, PHP code can be edited.
CVE-2019-15780 1 Strategy11 1 Formidable Form Builder 2022-04-18 7.5 HIGH 9.8 CRITICAL
The formidable plugin before 4.02.01 for WordPress has unsafe deserialization.
CVE-2021-24608 1 Strategy11 1 Formidable Form Builder 2021-10-27 3.5 LOW 4.8 MEDIUM
The Formidable Form Builder – Contact Form, Survey & Quiz Forms Plugin for WordPress plugin before 5.0.07 does not sanitise and escape its Form's Labels, allowing high privileged users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed