PushEngage · Security record
Is PushEngage safe?
No known vulnerability affects the current version (4.3.0). 1 issue was found in earlier versions and fixed, the latest disclosed on Jun 10, 2026.
Checked 4 days ago against the WPVulnerability database, for version 4.3.0.
How it’s looked after
- Last release
- Nov 5, 2026 (4 days ago)
- Releases in the last year
- 14
- Tested up to
- WordPress 7.1.4
- Active installs
- 8K+
1 known vulnerability
- 1 high
None affects the current version.
Every known vulnerability in PushEngage
Newest first, with any that affect the current version at the top.
Fixed in 4.2.4 · CVE-2026-52698 · Jun 10, 2026 · Wordfence
Questions about PushEngage’s security
Is PushEngage safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep PushEngage updated: most attacks target sites that haven’t updated.
Does PushEngage have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep PushEngage up to date.
Is PushEngage still maintained?
Yes. Its last release was 4 days ago. No support threads were opened in the last two months.
Is PushEngage compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.