CVE-2026-92086

MW WP Form <= 5.1.7 - Unauthenticated Sensitive Information Exposure in 'post_id' Parameter

2026-10-28 21:32
RIA Labs

Strategic Overview

Status
Patched in 5.1.8
Affected Plugin
MW WP Form
Affected Version
<= 5.1.7
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-92086
View all MW WP Form vulnerabilities

At a glance

CVE-2026-92086 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the MW WP Form WordPress plugin, affecting versions <= 5.1.7. 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.8; sites on affected versions should update now. Disclosed October 2026, reported by RIA Labs.

Vulnerability Overview

The MW WP Form plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.1.7 via the 'post_id' parameter. This makes it possible for unauthenticated attackers to extract personally identifiable information from other users' form inquiry records, including submitted names, email addresses, and free-text message bodies, by enumerating sequential post IDs. Exploitation requires the targeted form to have the querystring setting enabled, but this is a standard documented feature of the plugin.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

MW WP Form <= 5.1.7 carries this weakness at post_id, and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For MW WP Form the fix is 5.1.8: builds <= 5.1.7 are affected, anything from 5.1.8 onward is not.

Remediation

Update to version 5.1.8, 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.8 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-92086https://www.wordfence.com/threat-intel/vulnerabilities/id/7e412f8a-f872-47cf-bbce-554b3559ef8ahttps://nvd.nist.gov/vuln/detail/CVE-2026-92086

Related records

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