CVE-2026-6206

MW WP Form <= 5.1.2 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'post_id' Query Parameter

2026-05-13 19:51
alex_henry20

Strategic Overview

Status
Patched in 5.1.3
Affected Plugin
MW WP Form
Affected Version
<= 5.1.2
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-6206
View all MW WP Form vulnerabilities

At a glance

CVE-2026-6206 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the MW WP Form WordPress plugin, affecting versions <= 5.1.2. 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 5.1.3; sites on affected versions should update now. Disclosed May 2026, reported by alex_henry20.

Vulnerability Overview

The MW WP Form plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 5.1.2 via the _get_post_property_from_querystring() function due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to.

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-639: Authorization Bypass Through User-Controlled Key

MW WP Form <= 5.1.2 carries this weakness at _get_post_property_from_querystring(), and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For MW WP Form the fix is 5.1.3: builds <= 5.1.2 are affected, anything from 5.1.3 onward is not.

Remediation

Update to version 5.1.3, 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: MW WP Form 5.1.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-6206https://www.wordfence.com/threat-intel/vulnerabilities/id/7f2c39f6-3d37-4765-99e8-023610856b61https://nvd.nist.gov/vuln/detail/CVE-2026-6206

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C