PushEngage – Web Push Notifications, WooCommerce Automation & Chat Widget <= 4.2.3 - Authenticated (Subscriber+) Information Exposure
Strategic Overview
- Status
- Patched in 4.2.4
- Affected Version
<= 4.2.3- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-52698
At a glance
CVE-2026-52698 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the PushEngage WordPress plugin, affecting versions <= 4.2.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.2.4; sites on affected versions should update now. Disclosed June 2026, reported by Jakub Herman.
Vulnerability Overview
The PushEngage – Web Push Notifications, WooCommerce Automation & Chat Widget plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.2.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive user or configuration data.
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 interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in PushEngage <= 4.2.3 takes an account at Subscriber level or above. 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 PushEngage the fix is 4.2.4: builds <= 4.2.3 are affected, anything from 4.2.4 onward is not.
Remediation
Update to version 4.2.4, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: PushEngage 4.2.4 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C