Skip to main content
Menu
CVEs

WPZOOM Forms authorization bypass exposes form submission PII

CVE-2026-131686Published , updated

6.5MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The WPZOOM Forms – Drag & Drop Contact Form Builder for WordPress plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.0.12 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to view the Name, Email address, and message excerpt stored in the _wpzf_fields meta of every form submission site-wide, regardless of submission ownership. Because public form submissions are stored with post_author=0, WordPress's built-in author-scoping guard in WP_Posts_List_Table is bypassed for Contributors who own zero submissions, causing the list query to return all submissions site-wide rather than only the authenticated user's own records.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131686 (WPZOOM Forms <= 2.0.12 - Missing Authorization to Authenticated (Contributor+) Form Submission PII Disclosure via 'wpzf-submission' Post…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131686 (entry last updated 2026-11-20):
Affected:
- wpzoom WPZOOM Forms – Drag & Drop Contact Form Builder for WordPress: through 2.0.12
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131686 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131686 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/3b9befb3-8052-4f54-af0c-87cc6589d268?source=cve
- https://plugins.trac.wordpress.org/browser/wpzoom-forms/tags/2.0.12/wpzoom-forms.php#L286
- https://plugins.trac.wordpress.org/browser/wpzoom-forms/tags/2.0.12/wpzoom-forms.php#L1394
- https://plugins.trac.wordpress.org/browser/wpzoom-forms/tags/2.0.12/classes/class-wpzoom-forms-submission-handler.php#L291
- https://wordpress.org/plugins/wpzoom-forms/#developers
- https://plugins.trac.wordpress.org/changeset/3808762/wpzoom-forms/trunk/wpzoom-forms.php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131686
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131686"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

Questions about CVE-2026-131686

Is CVE-2026-131686 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-131686?

WPZOOM Forms – Drag & Drop Contact Form Builder for WordPress: through 2.0.12.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.