CVE-2022-45803

Gutenberg Forms <= 2.2.8.3 - Authenticated(Subscriber+) Sensitive Information Disclosure

2023-02-06 00:00
Nguyen Anh Tien

Strategic Overview

Status
Patched in 2.2.9
Affected Version
<= 2.2.8.3
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-45803
View all Gutenberg Forms – WordPress Form Builder Plugin vulnerabilities

At a glance

CVE-2022-45803 is a medium-severity Missing Authorization vulnerability in the Gutenberg Forms WordPress plugin, affecting versions <= 2.2.8.3. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.2.9; sites on affected versions should update now. Disclosed February 2023, reported by Nguyen Anh Tien.

Vulnerability Overview

The Gutenberg Forms plugin for WordPress is vulnerable to Sensitive Information Disclosure in versions up to, and including, 2.2.8.3, due to insufficient access control on form entries. This allowed authenticated attackers with subscriber-level privileges and above to view the contents of form entries.

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 interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-862: Missing Authorization

Reaching this weakness in Gutenberg Forms <= 2.2.8.3 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Gutenberg Forms the fix is 2.2.9: builds <= 2.2.8.3 are affected, anything from 2.2.9 onward is not.

Remediation

Update to version 2.2.9, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Gutenberg Forms 2.2.9 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