CVE-2022-0163

Smart Forms < 2.6.71 - Missing Authorization to Sensitive Information Disclosure

2022-02-14 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 2.6.71
Affected Version
< 2.6.71
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-0163
View all Smart Forms – when you need more than just a contact form vulnerabilities

At a glance

CVE-2022-0163 is a medium-severity Missing Authorization vulnerability in the Smart Forms WordPress plugin, affecting versions < 2.6.71. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.6.71; sites on affected versions should update now. Disclosed February 2022, reported by Krzysztof Zając.

Vulnerability Overview

The Smart Forms WordPress plugin before 2.6.71 does not have authorisation in its rednao_smart_forms_entries_list AJAX action, allowing any authenticated users, such as subscriber, to download arbitrary form's data, which could include sensitive information such as PII depending on the form.

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 Smart Forms < 2.6.71 takes a caller who can reach the endpoint. 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 Smart Forms the fix is 2.6.71: builds < 2.6.71 are affected, anything from 2.6.71 onward is not.

Remediation

Update to version 2.6.71, 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: Smart Forms 2.6.71 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