CVE-2023-7203

Smart Forms <= 2.6.86 - Missing Authorization

2024-02-02 00:00
Mohammad Reza Omrani

Strategic Overview

Status
Patched in 2.6.87
Affected Version
<= 2.6.86
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-7203
View all Smart Forms – when you need more than just a contact form vulnerabilities

At a glance

CVE-2023-7203 is a medium-severity Missing Authorization vulnerability in the Smart Forms WordPress plugin, affecting versions <= 2.6.86. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.6.87; sites on affected versions should update now. Disclosed February 2024, reported by Mohammad Reza Omrani.

Vulnerability Overview

The Smart Forms – when you need more than just a contact form plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the rednao_smart_form_delete_entries() AJAX action in all versions up to, and including, 2.6.86. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete 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.

CWE-862: Missing Authorization

Smart Forms <= 2.6.86 carries this weakness at rednao_smart_form_delete_entries(), and reaching it 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.87: builds <= 2.6.86 are affected, anything from 2.6.87 onward is not.

Remediation

Update to version 2.6.87, 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.87 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