Skip to main content

Visual Form Builder EUVDEUVD-2026-102689

| CVE-2026-105974 MEDIUM
Information Exposure (CWE-200)
2026-10-16 WPScan GHSA-j8xw-rmx7-c7p2
4.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register or obtain Subscriber account
  2. Exploit
    Authenticate to WordPress dashboard
  3. Execution
    Load unprotected form-submissions widget
  4. Impact
    Read other users' contact data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated WordPress account at Subscriber level or above (PR:L) on a site running Visual Form Builder plugin version ≤3.1; the attacker must be able to reach the wp-admin dashboard where the vulnerable recent-submissions widget renders. The specific feature at fault is the dashboard widget that displays recent form submission data without performing an authorization/capability check. Limiting factors: exploitation is impossible without a valid low-privilege account, so sites that disable open user registration or do not grant dashboard access to untrusted users are not realistically exposed; impact is confined to read-only disclosure of names, email addresses, form titles and timestamps (no write, no takeover). No user interaction is required (UI:N).

Impact

This is a genuinely low-priority vulnerability despite being a real flaw, and the multiple signals are consistent rather than conflicting. The CVSS 3.1 base score of 4.3 (Medium) is driven by network vector (AV:N) and low complexity (AC:L) but is correctly held down by PR:L (an authenticated Subscriber account is required) and limited impact (C:L/I:N/A:N - read-only disclosure of non-sensitive contact fields). EPSS reinforces low real-world urgency at 0.15% (4th percentile), and the CVE is NOT in CISA KEV (exploitation status: none per SSVC). SSVC further rates it Automatable: no and Technical Impact: partial, meaning there is no reliable path to mass automated exploitation. The one elevating signal is that publicly available exploit code exists (WPScan), but POC availability is distinct from active exploitation and does not change the picture here. Net: a WordPress site that allows open/low-privilege user registration faces a plausible but minor information-disclosure risk; sites that do not grant Subscriber accounts to untrusted users face negligible risk. All signals agree this is a low-severity, low-likelihood issue, not a high-CVSS/low-real-risk mismatch.

Exploit ScenarioDerived

An attacker who holds or self-registers a low-privilege Subscriber account on a WordPress site running Visual Form Builder ≤3.1 logs into the admin dashboard and views the plugin's recent-submissions dashboard widget, which omits any authorization check. They harvest other users' submitted names, email addresses, form titles and timestamps. A public POC exists (WPScan), and because the vector is network-based with low complexity, exploitation is trivial once the attacker has any authenticated session.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 16, 2026

The Visual Form Builder WordPress plugin through version 3.1 renders a wp-admin dashboard widget that lists recent form submissions without performing any capability or authorization check, so any authenticated user at Subscriber level or above can read other users' submitted contact information - names, email addresses, form titles and timestamps. Exploitation requires a valid low-privilege WordPress account (CVSS PR:L) and the ability to reach the dashboard where the widget loads, and the impact is confined to read-only disclosure with no data modification or account takeover. Publicly available exploit code exists, but there is no confirmed active exploitation, no CISA KEV listing, and the EPSS score is negligible at 0.15% (4th percentile), so this is a genuinely low-priority issue that is nonetheless a real and easily fixed flaw.

RemediationAI

No vendor-released patch was identified at time of analysis, and no fixed version number appears anywhere in the available intelligence - do not assume that any specific release above 3.1 is patched until the vendor or WPScan confirms it, and check the WPScan advisory at https://wpscan.com/vulnerability/ab69c0b2-e18d-495c-b6a3-546f4fe4c5d9/ and the plugin's WordPress.org/ vendor page for an updated release. Because the root cause is a missing current_user_can() check in the dashboard widget callback, the highest-value compensating control is to eliminate the attacker's prerequisite: disable open user registration in WordPress settings (or restrict it to invite-only), which removes the Subscriber-level foothold the vulnerability requires - the trade-off is that legitimate self-service signups must be handled another way, such as a moderated registration plugin. If untrusted accounts must exist, restrict their dashboard access (for example with a role-management or admin-restriction plugin, or by removing the 'read' capability for untrusted roles) so they cannot load wp-admin at all; the trade-off is that those users also lose any legitimate profile or front-end account screens. Alternatively, deactivate or uninstall Visual Form Builder if form submissions do not need to be reviewed in the dashboard - the trade-off is loss of form functionality and stored submissions - or add a small mu-plugin that unregisters the affected dashboard widget via remove_meta_box()/remove_action() on wp_dashboard_setup, which preserves the plugin's front-end forms while cutting off the disclosure path but requires code maintenance and re-verification after each plugin update. Additionally, treat the leaked data as exposed: monitor for follow-on phishing against the affected form submitters, since names, email addresses, form titles and timestamps can be harvested in bulk by any registered user, and review whether historical submissions contain any data that would make that exposure more than a privacy nuisance.

Affected VersionsENISA

Visual Form Builder 0 ≤3.1

Affected Packages

euvd visual_form_builder no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic missing-authorization defect (CWE-200, exposure of sensitive information to an unauthorized actor) in a WordPress plugin's admin dashboard widget. WordPress plugins register widgets through the wp_dashboard_setup hook, and the rendering callback is responsible for calling current_user_can() with an appropriate capability - for submission data that would typically be manage_options or an editor/administrator-level capability. Visual Form Builder's recent-submissions widget omits that check, so the widget's data-fetching and rendering path executes for any logged-in account whose role can view wp-admin, which by default includes Subscriber. Because the disclosure happens server-side in the dashboard page body, the attacker simply loads the dashboard; no form submission, no crafted payload, and no user interaction (UI:N) is required, and the attack is network-delivered (AV:N) with low complexity (AC:L). The CPE string recorded for this issue is cpe:2.3:a:unknown:visual_form_builder:*:*:*:*:*:*:*:*, with the vendor component left unassigned in the NVD CPE dictionary, and the ENISA EUVD entry describes the affected range as 'Visual Form Builder 0 ≤3.1' - an indication that the product's version mapping is still being normalised rather than a sign of an unusual deployment topology. The CVSS 3.1 base of 4.3 reflects scope-unchanged, confidentiality-only impact (S:U/C:L/I:N/A:N) and an authenticated prerequisite, and the CISA SSVC decision points (Exploitation: none, Automatable: no, Technical Impact: partial) align with that low-severity reading. Per our independent assessment, exploitation is impossible without a valid low-privilege WordPress account, so sites that disable open registration or that withhold dashboard access from untrusted users are not realistically exposed; the residual risk is limited to privacy exposure of contact-form content.

Know when Visual Form Builder gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 4.3 MEDIUM

Remote and low-complexity, but a Subscriber account is required so PR:L; only limited read of others' contact data, hence C:L with I:N and A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

3
CVSS changed
Oct 16, 2026 - 15:23 NVD
4.3 (MEDIUM)
CVE Published
Oct 16, 2026 - 06:00 cve.org
MEDIUM 4.3
CVE Published
Oct 16, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Visual Form Builder WordPress plugin through 3.1 does not perform an authorization check before displaying recent form submission data in a dashboard widget, allowing any authenticated user (Subscriber and above) to read other users' submitted contact information, including names, email addresses, form titles and timestamps.

Threat Intelligence Overview

EPSS Score
0.1%
Top 96% exploitable
Prevalence
Medium
common WordPress form plugin, moderate install base, not ubiquitous core software
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy