Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-15748 – Unauthenticated Arbitrary File Upload / RCE – Forminator Forms plugin (WordPress) ≤

Be the first to know when new zero-days emerge:

Summary

CVE-2026-15748 is a critical arbitrary file upload vulnerability (CWE-434) in the Forminator Forms plugin for WordPress, affecting all versions up to and including 1.56.1. The flaw allows unauthenticated attackers to upload executable PHP files, which can lead to remote code execution and full site takeover. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: the plugin’s handle_file_upload function relies on a dangerous-extension blocklist that performs exact-key matching, which can be bypassed using pipe-alternative MIME type keys.
  • This weak validation is combined with a public form submission handler that accepts attacker-controlled upload field configuration, allowing an attacker to influence what is treated as an allowed file type.
  • Trigger conditions: the targeted site must have a form that contains both a File Upload field and a Select field.
  • Attack vector: network, no authentication or user interaction required — an attacker submits a crafted form request directly to the public-facing form endpoint.
  • Impact: successful exploitation allows uploading executable files (e.g., PHP webshells) to the server, enabling remote code execution and complete compromise of the affected WordPress site.

Affected software

  • Forminator Forms – Contact Form, Payment Form & Custom Form Builder (WordPress plugin by WPMU DEV): all versions up to and including 1.56.1

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Update Forminator Forms to version 1.56.2 or later, which addresses the file type validation flaw.
  • If immediate patching is not possible: review any forms that combine a File Upload field with a Select field and disable or restrict them until patched; audit upload directories for unexpected or executable files (e.g., .php); ensure custom upload directories enforce execution restrictions (e.g., via .htaccess or web server configuration).
  • After patching: audit server logs and upload directories for signs of prior exploitation, and rotate credentials/secrets if compromise is suspected.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/forminator/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge