Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain low-privileged WordPress account
-
DeliveryAuthenticate to target site
-
ExploitSend crafted request to vulnerable PushEngage endpoint
-
ExecutionReceive subscriber data in response
-
ImpactHarvest subscriber records for follow-on abuse
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Outbound data filtering
|
| Exploitation Conditions | Exploitation requires (1) a WordPress site with the PushEngage - Web Push Notifications, eCommerce Automation & Chat Widget plugin installed and active at version 4.2.3 or earlier, (2) network reachability to the site's admin-ajax or REST API surface, and (3) an authenticated session at a low privilege level (PR:L per the CVSS vector - typically Subscriber or Contributor, achievable on sites that allow open user registration). Exploitation is limited by the need for any authenticated account, so sites that disable public registration and tightly control low-privileged accounts materially reduce risk; no user interaction by a victim is required (UI:N). |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L) shows network reachability, low complexity, low privileges required, no user interaction, and - notably - a scope change with low impact across all three CIA properties, yielding a 7.4 score driven largely by S:C rather than by severe individual impacts. There is no EPSS score, no CISA KEV listing, and no POC referenced in the supplied intelligence, so real-world exploitation pressure appears low at this time despite the elevated CVSS. The I:L and A:L ratings are worth scrutinizing because a CWE-201 disclosure bug usually maps to C:L only; the vendor's choice of I:L/A:L is not explained in the Patchstack reference summary and should be verified against the full Patchstack advisory before treating this as more than a confidentiality issue. |
| Exploit ScenarioDerived | An attacker who has registered or obtained any low-privileged WordPress account (e.g., Subscriber or Contributor) on a site running PushEngage <= 4.2.3 authenticates and issues a crafted request to a PushEngage endpoint that returns subscriber data. The response leaks subscriber records belonging to the site, allowing the attacker to harvest a list of push-notification subscribers for phishing, spam, or follow-on targeting. No public exploit identified at time of analysis, but the low complexity and authenticated-only barrier make this trivially reproducible once the vulnerable endpoint is known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 17, 2026
Sensitive data exposure in the PushEngage WordPress plugin (versions <= 4.2.3) allows authenticated low-privileged users to access subscriber information that should remain protected. The flaw, reported by Patchstack and tracked as CWE-201 (Insertion of Sensitive Information Into Sent Data), affects WordPress sites running the Web Push Notifications, eCommerce Automation & Chat Widget plugin and carries a CVSS 3.1 score of 7.4 with a scope change. No public exploit identified at time of analysis.
RemediationAI
Patch available per vendor advisory - upgrade the PushEngage plugin to a version newer than 4.2.3 as published on the WordPress.org plugin repository, consulting the Patchstack record at https://patchstack.com/database/wordpress/plugin/pushengage/vulnerability/wordpress-pushengage-web-push-notifications-ecommerce-automation-chat-widget-plugin-4-2-3-sensitive-data-exposure-vulnerability for the exact fixed release. If immediate patching is not possible, deactivate the PushEngage plugin (which will stop push notifications and the chat widget until restored), or restrict access to wp-admin and the WordPress REST/AJAX surface to trusted IPs via a web application firewall or .htaccess rule - accepting that this blocks legitimate low-privileged contributors and subscribers from any plugin functionality they were entitled to. As an interim hardening step, audit which roles can authenticate to the site and remove any low-privileged accounts that are not strictly required, since the flaw requires PR:L access.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PushEngage is a WordPress plugin (CPE: syed_balkhi:pushengage) used by site owners to send web push notifications, run eCommerce automations, and operate a chat widget. The underlying weakness is CWE-201 (Insertion of Sensitive Information Into Sent Data), a class of bug where an application includes sensitive data - here, subscriber records - in a response or output that is accessible to actors who should not see it. In WordPress plugin contexts this typically manifests as an AJAX action, REST endpoint, or admin-ajax handler that fails to enforce capability checks proportional to the sensitivity of the data being returned, leaking subscriber identifiers, endpoints, or contact data across the user/role boundary.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
Authenticated low-privileged WordPress user reads subscriber data over the network; CWE-201 is a confidentiality-only disclosure, so I:N/A:N and no scope change.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Sensitive Data Exposure in PushEngage - Web Push Notifications, eCommerce Automation & Chat Widget <= 4.2.3 versions.
Executive ViewAI
The PushEngage WordPress plugin 'Web Push Notifications, eCommerce Automation & Chat Widget' (versions ≤4.2.3) contains a sensitive data exposure vulnerability (CWE-201) that allows low-privileged authenticated users to access subscriber information without authorization. No public exploit identified at time of analysis, but this flaw directly exposes customer data to internal user access abuse, creating privacy and compliance liability for WordPress sites. Immediate remediation is required to contain exposure risk.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) immediately deactivate the plugin to eliminate attack surface; (2) restrict plugin administrative access to WordPress administrators only via role-based permissions; (3) implement database-level query restrictions on subscriber data tables; (4) enable WordPress audit logging to detect low-privileged user access attempts on subscriber information; (5) evaluate alternative push notification platforms for permanent replacement.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-37626
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB