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-114180 Overview
CVE-2026-114180 is a Missing Authorization vulnerability [CWE-862] affecting the Wpmet Metform plugin for WordPress. The flaw stems from incorrectly configured access control security levels, allowing unauthenticated attackers to interact with plugin functionality that should require privileged access. The issue affects all Metform versions up to and including 4.3.2.
The vulnerability is network-exploitable, requires no privileges, and needs no user interaction. Successful exploitation can lead to limited integrity impact on affected WordPress sites running the plugin. Site administrators using Metform for form building should treat this as a priority remediation item.
Critical Impact
Unauthenticated remote attackers can abuse broken access control in Metform ≤ 4.3.2 to modify plugin-managed data without proper authorization checks.
Affected Products
- Wpmet Metform plugin for WordPress
- All versions from unspecified initial release through 4.3.2
- WordPress sites with the Metform form builder plugin installed and active
Discovery Timeline
- 2026-10-22 - CVE-2026-114180 published to the National Vulnerability Database
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114180
Vulnerability Analysis
The vulnerability resides in the Metform WordPress plugin, a drag-and-drop form builder widely deployed with the Elementor page builder. Metform exposes multiple endpoints for form configuration, submission handling, and administrative operations. One or more of these endpoints lack proper authorization enforcement.
Attackers can reach vulnerable handlers directly over the network without authenticating to WordPress. The result is a Broken Access Control condition in which security-sensitive functionality is reachable by users who should not have access. The CVSS vector indicates a limited integrity impact with no confidentiality or availability impact.
Root Cause
The root cause is a missing or insufficient authorization check [CWE-862] in Metform plugin endpoints. The affected code paths likely fail to invoke WordPress capability checks such as current_user_can() or nonce validation via check_ajax_referer() before executing privileged operations. Without these checks, the plugin treats requests from unauthenticated or low-privilege users as if they originated from administrators.
Attack Vector
An attacker sends crafted HTTP requests to the vulnerable Metform endpoint on a target WordPress site. Because no privileges or user interaction are required, exploitation can be performed at scale against internet-exposed WordPress installations. The attacker leverages the broken access control to perform plugin actions reserved for authorized users, resulting in unauthorized modification of plugin-managed state. See the Patchstack Metform Plugin Vulnerability advisory for technical details.
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 AttacksDetection Methods for CVE-2026-114180
Indicators of Compromise
- Unexpected changes to Metform form configurations, submission records, or related plugin options in the WordPress database
- Unauthenticated POST or GET requests to Metform REST or AJAX endpoints in web server access logs
- New or modified form entries that do not correlate with legitimate authenticated administrator sessions
Detection Strategies
- Inspect web server logs for requests to /wp-json/metform/ and admin-ajax.php actions prefixed with metform_ originating from clients without active WordPress authentication cookies
- Compare the installed Metform plugin version against the fixed release and flag any instance at or below version 4.3.2
- Correlate anomalous plugin configuration changes with the absence of a corresponding authenticated administrator session
Monitoring Recommendations
- Enable WordPress audit logging for all plugin option changes and form configuration updates
- Monitor outbound requests from the web server to detect secondary payloads or callbacks that may follow successful exploitation
- Alert on sudden spikes in requests to Metform endpoints across hosted WordPress fleets
How to Mitigate CVE-2026-114180
Immediate Actions Required
- Identify all WordPress sites running the Metform plugin and inventory their versions
- Upgrade Metform to a release later than 4.3.2 as soon as the vendor publishes a patched version
- If a patched version is not yet available, deactivate and remove the Metform plugin on exposed sites
- Review recent form submissions and plugin configuration changes for signs of unauthorized modification
Patch Information
At publication time, the Patchstack advisory identifies the vulnerable range as Metform versions through 4.3.2. Site operators should consult the Wpmet changelog and the WordPress plugin repository for the fixed release and apply it through the WordPress plugin updater or WP-CLI.
Workarounds
- Restrict access to the WordPress REST API and admin-ajax.php using a web application firewall rule that blocks unauthenticated requests to Metform-specific actions
- Place the WordPress administration interface behind IP allowlisting or an authenticating reverse proxy
- Temporarily disable the Metform plugin on production sites until a patched version is validated in staging
# Example: upgrade Metform via WP-CLI once a fixed version is released
wp plugin update metform --version=<fixed-version>
# Verify installed version
wp plugin get metform --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

