CVE-2022-0140

Visual Form Builder <= 3.0.5 - Unauthenticated Information Disclosure

2021-11-03 00:00
Vishnupriya Ilango

Strategic Overview

Status
Patched in 3.0.6
Affected Plugin
Visual Form Builder
Affected Version
< 3.0.6
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2022-0140
View all Visual Form Builder vulnerabilities

At a glance

CVE-2022-0140 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Visual Form Builder WordPress plugin, affecting versions < 3.0.6. 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 3.0.6; sites on affected versions should update now. Disclosed November 2021, reported by Vishnupriya Ilango.

Vulnerability Overview

The Visual Form Builder WordPress plugin before 3.0.6 does not perform access control on entry form export, allowing unauthenticated users to see the form entries or export it as a CSV File using the vfb-export endpoint.

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

Reaching this weakness in Visual Form Builder < 3.0.6 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 Visual Form Builder the fix is 3.0.6: builds < 3.0.6 are affected, anything from 3.0.6 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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