Forminator Forms – Contact Form, Payment Form & Custom Form Builder Plugin Vulnerability (CVE-2026-120676)

On this page

Security Alert Summary

The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is affected by a stored cross-site scripting (XSS) vulnerability (CVE-2026-120676). The issue allows unauthenticated attackers to inject scripts via the File Upload field parameter upload-1 when the field remains at plugin defaults and the server does not map a Content-Type for the .rtx extension. Injected scripts execute whenever a user accesses an affected page.

CVE Details

  • CVE ID: CVE-2026-120676
  • Affected component: Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress
  • Affected versions: all versions up to and including 1.58.4
  • Published: November 21, 2026 at 8:16:38 AM
  • Last modified: November 21, 2026 at 8:16:38 AM
  • CVSS v3.1: Base Score 7.2, Severity HIGH, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
  • Authentication / Privileges / User interaction: No authentication required; Privileges required: None; User interaction: None
  • Primary impact: Confidentiality: Low; Integrity: Low; Availability: None
  • Weakness: CWE-79 (Cross-site Scripting)

Technical Details

This vulnerability is a stored XSS caused by insufficient input sanitization and insufficient output escaping for data submitted via the Forminator File Upload field. The exploitable parameter is the File Upload field’s element_id (documented as upload-1 in the report). When the File Upload field is left at the plugin default settings (no custom-files restriction configured), an attacker can submit content that includes executable script payloads which are persisted by the plugin and later rendered into pages viewed by other users.

Exploitation also requires that the server does not map any Content-Type to the .rtx extension. The lack of a mapped Content-Type for .rtx is noted as the default behavior for the Debian/Ubuntu Apache package used by the official WordPress Docker image and by many shared hosts; in that configuration, the uploaded content may be served in a way that allows browser interpretation of embedded scripts.

The report notes this issue is an incomplete fix for a prior vulnerability (CVE-2024-1794). The practical effect is that attackers can inject scripts that execute in the context of users who view the affected pages, consistent with the CVSS impacts of confidentiality and integrity being rated as Low and availability as None.

How This Could Impact Your Website

Consider a site with multiple WordPress users: the site owner, several internal staff members who manage content, and an external contractor who occasionally uploads files via forms. If a Forminator form uses the default File Upload field and an attacker uploads a crafted file, the injected script can run when staff or the contractor view the form entries or any page that renders the uploaded data. Possible real outcomes include exposure of internal user email addresses or other information visible to the page, and an increased risk of targeted phishing or social engineering against staff whose accounts or contact details are exposed.

If youre unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review your setup.

Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles and capabilities, especially for contributor-level accounts and external contractors.
  • Enforce strong passwords and two-factor authentication for editor and administrator accounts.
  • Remove unused or unmaintained plugins to reduce attack surface.
  • Monitor site activity and logs for unusual behavior related to form submissions and file uploads.

If youd like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References