CVE-2021-36915

Profile Builder – User Profile & User Registration Forms <= 3.6.4 - Cross-Site Request Forgery

2022-09-29 00:00
mirphak

Strategic Overview

At a glance

CVE-2021-36915 is a high-severity Missing Authorization vulnerability in the User Profile Builder WordPress plugin, affecting versions <= 3.6.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.6.5; sites on affected versions should update now. Disclosed September 2022, reported by mirphak.

Vulnerability Overview

The Profile Builder – User Profile & User Registration Forms plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.6.4. This is due to missing nonce validation on the wppb_pbie_import() & wppb_pbie_export_our_json() functions. This makes it possible for unauthenticated attackers to import and export plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

User Profile Builder <= 3.6.4 carries this weakness at wppb_pbie_import(), 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 User Profile Builder the fix is 3.6.5: builds <= 3.6.4 are affected, anything from 3.6.5 onward is not.

Remediation

Update to version 3.6.5, 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: User Profile Builder 3.6.5 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