Skip to main content

PushEngage WordPress Plugin EUVDEUVD-2026-37626

| CVE-2026-52698 HIGH
Insertion of Sensitive Information Into Sent Data (CWE-201)
2026-06-17 Patchstack
7.4
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register or obtain low-privileged WordPress account
  2. Delivery
    Authenticate to target site
  3. Exploit
    Send crafted request to vulnerable PushEngage endpoint
  4. Execution
    Receive subscriber data in response
  5. Impact
    Harvest 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

PushEngage – Web Push Notifications, eCommerce Automation &amp; Chat Widget n/a ≤4.2.3

Affected Packages

euvd pushengage_web_push_notifications_ecommerce_automation_amp_chat_widget no fix

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

Vendor (Patchstack) PRIMARY 7.4 HIGH
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
vuln.today AI 4.3 MEDIUM

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.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

DescriptionCVE.org

Subscriber Sensitive Data Exposure in PushEngage - Web Push Notifications, eCommerce Automation &amp; Chat Widget <= 4.2.3 versions.

Executive ViewAI

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.2%
Top 88% exploitable
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +37
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy