Security Scorecard for Forminator Forms Plugin for WordPress

Checked on November 23, 2024

Grade:

F

Issues the Plugin's Developer Should Address:


  • The plugin handles a file upload using a function that doesn't include security checks, which could allow for malicious files to be uploaded.

  • The PHP function filter_input() is used with the FILTER_DEFAULT filter, which doesn't do any filtering.

  • The PHP function filter_input() is used without a filter, so it doesn't do any filtering.

  • The plugin is using the WordPress function maybe_unserialize(), which is missing PHP's feature to protect against PHP object injection. A Core Committer of WordPress indicated that it would not be a good idea for plugins to be using the function.

  • The plugin doesn't contain a security.txt file (or alternatively a SECURITY.md or SECURITY-INSIGHTS.yml), which would provide information on how to report security issues to the developer.

  • The plugin isn't listing in a security.txt file where the results of a security review that has been done of the plugin can be found. A well done security review would provide a good measure of the security of the plugin at the time it was done.

  • The plugin isn't listing in a security.txt file where a software bill of materials (SBOM), which provides information on what third-party software is included in the plugin, can be found. That limits the ability to access the security of that third-party software.

  • It is being claimed by a security provider that the plugin's developer is redirecting attempts to report security issues to a third-party. That third-party is known to not properly handle vulnerabilities and mislead others, including developers, into believeing they have been fixed when they haven't. And that third-party also doesn't accept reporting all security issues, leading to nowhere to report many security issues. It is important for developers to have their own mechanism for reporting security issues to them.

Resolving those issues would bring the plugin's grade up to an A+. You can notify the developer of the issues here. If the developer is interested in resolving those issues, we would be happy to help them to get started doing that.

You can also can consider using a similar plugin that is already more secure or one where the developer is interested in making their plugin more secure.

Additional Security Information

Plugin Information

Previous Grades

  • July 26, 2024:    C

Grades for Other Contact Form Plugins

  1. Fluent Forms     B+
  2. MetForm     B+
  3. Flo Forms     B
  4. Smart Forms     B
  5. Contact Form 7     C+
  6. Formidable Forms     C+
  7. WPForms     C+
  8. WS Form LITE     C
  9. Ninja Forms     F

Grades for Other Form Plugins

  1. Newsletter, SMTP, Email marketing and Subscribe forms by Brevo (formely Sendinblue)     A
  2. MetForm     B+
  3. FormCraft     B
  4. HubSpot     B
  5. Smart Forms     B
  6. Formidable Forms     C+
  7. WPForms     C+
  8. WS Form LITE     C
  9. Ninja Forms     F

Check Another Plugin





Check Plugin Not in WordPress Plugin Directory

Subscribers of our service can submit ZIP files of plugins that are not in the WordPress Plugin Directory to have them checked. (Not all issues can be checked for with uploaded plugins, as they require data not available with just the plugin's files.) You can sign up for the service for free here. For existing subscribers, once you are logged in to your account, return to this page to access that functionality.

The results of these gradings will not be stored.

About the Scorecard

The Plugin Security Scorecard grades plugins' handling of security based on data coming from the Plugin Vulnerabilities service, checking over the contents of the plugin, the WordPress.org API, and data generated specifically for the tool. It provides a useful, but incomplete, understanding of the security posture of the plugin and its developer. All the issues identified are ones that the developer of the plugin has the ability to address to get the grade of the plugin up to an A+.

Grades are calculated based on issues with any of the following:

  • Plugins known to be vulnerable
  • Plugin developers with track records of improperly handling security problems
  • Security issues in the plugin that can be detected in an automated fashion
  • Issues with the developer's developerment processes that suggest that their could be problems with security
  • Plugins making unsupported, misleading, and false claims about their handling of security and the handling of security with WordPress

We are working to expand and refine the tools' ability to provide a good measure of plugins' security status. If you are aware of an additional security concern with this plugin that isn't represented here, please contact us. Other feedback on the tool is also welcome.

If you want a comprehensive understanding of the security of the plugin, a well-done security review is really needed to provide that.