CVE-2021-24654

User Registration < 2.0.2 - Authenticated Stored Cross-Site Scripting

2021-09-06 00:00
AyeCode Ltd

Strategic Overview

Status
Patched in 2.0.2
Affected Version
< 2.0.2
CVSS
5.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24654
View all WP User Manager – User Profile Builder & Membership vulnerabilities

At a glance

CVE-2021-24654 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP User Manager WordPress plugin, affecting versions < 2.0.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.0.2; sites on affected versions should update now. Disclosed September 2021, reported by AyeCode Ltd.

Vulnerability Overview

The User Registration WordPress plugin before 2.0.2 does not properly sanitise the user_registration_profile_pic_url value when submitted directly via the user_registration_update_profile_details AJAX action. This could allow any authenticated user, such as subscriber, to perform Stored Cross-Site attacks when their profile is viewed

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WP User Manager < 2.0.2 takes any authenticated account. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP User Manager the fix is 2.0.2: builds < 2.0.2 are affected, anything from 2.0.2 onward is not.

Remediation

Update to version 2.0.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP User Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP User Manager 2.0.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C