Forminator Forms <= 1.57.2.0 - Missing Authorization to Unauthenticated Arbitrary Post Meta Injection
Strategic Overview
- Status
- Patched in 1.57.2.1
- Affected Version
<= 1.57.2.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-87071
At a glance
CVE-2026-87071 is a medium-severity Missing Authorization vulnerability in the Forminator Forms WordPress plugin, affecting versions <= 1.57.2.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.57.2.1; sites on affected versions should update now. Disclosed September 2026, reported by Dion Mulaj.
Vulnerability Overview
The Forminator Forms plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.57.2.0. This is due to missing allowlist validation on meta keys supplied by form submissions, which allowed arbitrary and protected meta keys to be written without restriction. This makes it possible for unauthenticated attackers to inject arbitrary post metadata—including WordPress-reserved protected keys—into posts created by form submissions, potentially altering post behaviour or bypassing application logic.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Forminator Forms <= 1.57.2.0 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Forminator Forms the fix is 1.57.2.1: builds <= 1.57.2.0 are affected, anything from 1.57.2.1 onward is not.
Remediation
Update to version 1.57.2.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Forminator Forms 1.57.2.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.5CVE-2024-10402: Forminator Forms Authenticated (Contributor+) Form
CVE-2024-10402 - 6.5CVE-2026-6214: Forminator Forms Authenticated (Subscriber+) Scheduled
CVE-2026-6214 - 5.3CVE-2026-108486: Forminator Forms Missing Authorization
CVE-2026-108486 - 5.3CVE-2026-65459: Forminator Forms Missing Authorization
CVE-2026-65459
Other vulnerabilities in Forminator Forms – Contact Form, Payment Form & Custom Form Builder
- 9.8CVE-2026-15748: Forminator Forms <= 1.56.1 Arbitrary File Upload
CVE-2026-15748 - 9.8CVE-2024-28890: Forminator <= 1.28.1 Arbitrary File Upload
CVE-2024-28890 - 9.8CVE-2023-4596: Forminator <= 1.24.6 Arbitrary File Upload
CVE-2023-4596 - 9.1CVE-2026-92229: Forminator Forms Arbitrary Shortcode Execution
CVE-2026-92229 - 9.1CVE-2024-31077: Forminator <= 1.29.2 SQL Injection
CVE-2024-31077 - 8.8CVE-2026-28111: Forminator Forms Privilege Escalation
CVE-2026-28111 - 8.8CVE-2025-6463: Forminator Forms Arbitrary File Deletion Triggered
CVE-2025-6463 - 8.1CVE-2026-66583: Forminator Forms PHP Object Injection
CVE-2026-66583
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C