CVE-2023-44150

ProfilePress <= 4.13.2 - Information Disclosure via Debug Log

2023-10-02 00:00
Revan Arifio

Strategic Overview

At a glance

CVE-2023-44150 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor 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 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.13.3; sites on affected versions should update now. Disclosed October 2023, reported by Revan Arifio.

Vulnerability Overview

The ProfilePress plugin for WordPress is vulnerable to Information Exposure in versions up to, and including, 4.13.2 via the unprotected access of debug logs. This makes it possible for unauthenticated attackers to retrieve the debug log which may contain information like system errors which could contain sensitive information. CVE-2023-50882 appears to be a potential duplicate of this issue.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content <= 4.13.2 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content the fix is 4.13.3: builds <= 4.13.2 are affected, anything from 4.13.3 onward is not.

Remediation

Update to version 4.13.3, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content 4.13.3 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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