CVE-2023-41953

ProfilePress <= 4.13.1 Cross-Site Request Forgery via 'admin_notice'

2023-09-09 00:00
Abdi Pranata

At a glance

CVE-2023-41953 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content WordPress plugin, affecting versions < 4.13.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.13.2; sites on affected versions should update now. Disclosed September 2023, reported by Abdi Pranata.

Vulnerability Overview

The ProfilePress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.13.1. This is due to missing or incorrect nonce validation on the 'admin_notice' function. This makes it possible for unauthenticated attackers to dismiss admin notices granted they can trick a site administrator into performing an action such as clicking on a link. The impact of this vulnerability is unknown.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content < 4.13.2 carries this weakness at admin_notice, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content the fix is 4.13.2: builds < 4.13.2 are affected, anything from 4.13.2 onward is not.

Remediation

Update to version 4.13.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content 4.13.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