CVE-2023-4469

Profile Extra Fields by BestWebSoft <= 1.2.7 - Missing Authorization to Sensitive Information Exposure

2023-10-05 00:00
Alex Thomas

Strategic Overview

Status
Patched in 1.2.8
Affected Version
<= 1.2.7
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-4469
View all Profile Extra Fields by BestWebSoft vulnerabilities

At a glance

CVE-2023-4469 is a medium-severity Missing Authorization vulnerability in the Profile Extra Fields by BestWebSoft WordPress plugin, affecting versions <= 1.2.7. 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 1.2.8; sites on affected versions should update now. Disclosed October 2023, reported by Alex Thomas.

Vulnerability Overview

The Profile Extra Fields by BestWebSoft plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the prflxtrflds_export_file function in versions up to, and including, 1.2.7. This makes it possible for unauthenticated attackers to expose potentially sensitive user data, including data entered into custom fields.

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-862: Missing Authorization

Reaching this weakness in Profile Extra Fields by BestWebSoft <= 1.2.7 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 Profile Extra Fields by BestWebSoft the fix is 1.2.8: builds <= 1.2.7 are affected, anything from 1.2.8 onward is not.

Remediation

Update to version 1.2.8, 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: Profile Extra Fields by BestWebSoft 1.2.8 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