Skip to main content
Vulnerability Database/CVE-2026-96336

CVE-2026-96336: WPMU DEV Forminator Auth Bypass Vulnerability

CVE-2026-96336 is an authentication bypass by spoofing flaw in WPMU DEV Forminator plugin that enables identity spoofing attacks. This article covers the technical details, affected versions up to 1.57.2, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-96336 Overview

CVE-2026-96336 is an authentication bypass by spoofing vulnerability in the WPMU DEV Forminator plugin for WordPress. The flaw affects Forminator versions up to and including 1.57.2 and enables identity spoofing against the plugin's payment handling logic. According to the Patchstack advisory, the weakness manifests as a payment bypass, allowing attackers to submit forms as if payment had been completed without actually authorizing a valid transaction. The vulnerability is remotely exploitable over the network, requires no authentication, and needs no user interaction. It is tracked under CWE-290: Authentication Bypass by Spoofing.

Critical Impact

Unauthenticated attackers can spoof payment confirmation on Forminator forms, undermining the integrity of any form that gates content, orders, or services behind payment.

Affected Products

  • WPMU DEV Forminator plugin for WordPress
  • Forminator versions from n/a through 1.57.2
  • WordPress sites using Forminator payment forms (Stripe, PayPal, or similar integrations)

Discovery Timeline

  • 2026-10-09 - CVE-2026-96336 published to the National Vulnerability Database (NVD)
  • 2026-10-11 - Last updated in the NVD database

Technical Details for CVE-2026-96336

Vulnerability Analysis

Forminator is a WordPress plugin used to build forms, polls, quizzes, and payment-collecting submissions. The vulnerability resides in how Forminator validates the authenticity of a payment event tied to a form submission. An attacker can craft requests that spoof the identity or trust context used by the plugin to determine whether a submission has been paid for, bypassing the intended payment gate.

The impact is scoped to integrity, with no direct effect on confidentiality or availability of the host system. However, in commerce or donation workflows, integrity loss translates directly to financial loss and fraudulent submissions treated as legitimate by downstream business logic.

Root Cause

The root cause maps to CWE-290: the plugin trusts attacker-controllable input or an easily spoofable identifier to authenticate a payment-related action, rather than verifying it against a server-side authoritative source such as a signed webhook or an API call to the payment processor. Full technical details are documented in the Patchstack Vulnerability Report.

Attack Vector

The attack is network-based and unauthenticated. An attacker submits a Forminator payment form and manipulates the request parameters that the plugin uses to confirm payment, causing the submission to be accepted as paid. No credentials, user interaction, or elevated privileges are required. Any WordPress site running a vulnerable Forminator version with payment-enabled forms is reachable from the public internet by default.

No verified public proof-of-concept code is available at this time. Refer to the Patchstack advisory for additional context.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-96336

Indicators of Compromise

  • Form submissions marked as paid in Forminator entries without a matching charge in the Stripe, PayPal, or other payment processor dashboard.
  • Unusual POST requests to Forminator submission endpoints such as /wp-admin/admin-ajax.php with action=forminator_submit_form_* parameters from unexpected sources.
  • Spikes in completed form entries that do not reconcile with payment processor settlement reports.

Detection Strategies

  • Reconcile Forminator submission logs against payment processor transaction logs on a scheduled basis and alert on any mismatch.
  • Inspect WordPress access logs for repeated submissions to the same payment-enabled form from a single IP or user agent.
  • Deploy a Web Application Firewall (WAF) rule that monitors Forminator AJAX actions and flags payloads that omit or malform expected payment identifiers.

Monitoring Recommendations

  • Enable verbose logging on the WordPress site, including request bodies for Forminator endpoints, and forward logs to a centralized SIEM for correlation.
  • Monitor the WordPress plugin inventory for the installed Forminator version and alert when any site runs 1.57.2 or earlier.
  • Track payment processor webhook delivery and failure rates to detect attempts to replay or forge payment confirmation events.

How to Mitigate CVE-2026-96336

Immediate Actions Required

  • Update Forminator to the fixed version released by WPMU DEV, as referenced in the Patchstack advisory.
  • Audit all Forminator submissions received while a vulnerable version was deployed and reconcile them against payment processor records.
  • Reverse or cancel any fulfilled orders, content access grants, or services that cannot be matched to a verified payment.

Patch Information

WPMU DEV has released a patched version of Forminator addressing the payment bypass. All sites running Forminator 1.57.2 or earlier must upgrade. Confirm the installed version under Plugins > Installed Plugins in the WordPress admin console after upgrading, and clear any caching layers in front of the site.

Workarounds

  • Temporarily disable Forminator payment forms until the plugin is upgraded, replacing them with hosted checkout links from the payment processor.
  • Require server-side verification of payment via the processor's API or signed webhook before processing any Forminator submission as paid.
  • Restrict access to Forminator payment form endpoints behind a WAF rule set that enforces strict parameter validation.
bash
# Example WP-CLI commands to inventory and update Forminator across a WordPress site
wp plugin list --name=forminator --fields=name,status,version
wp plugin update forminator
wp plugin get forminator --field=version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.