Plugins · all-push-notification · data as of 2026-11-04
Is All push notification for WP safe? Known vulnerabilities and latest version
- Status
- Closed 2026-01-29
- Known issues on record
- 4
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate all-push-notification && wp plugin delete all-push-notification
Check your version
Known vulnerabilities
4 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 4 record(s) do not state which versions are affected.
medium 4.9 CVE-2026-0816 · published 2026-02-04
SQL injection in All push notification for WP (1.5.3 and older)
- Affected
- 1.5.3 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The All push notification for WP plugin for WordPress is vulnerable to time-based SQL Injection via the 'delete_id' parameter in all versions up to, and including, 1.5.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
high 7.1 CVE-2025-32546 · published 2025-04-17
Cross-site request forgery (CSRF) in All push notification for WP (1.5.3 and older)
- Affected
- 1.5.3 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in gtlwpdev All push notification for WP all-push-notification allows Reflected XSS.This issue affects All push notification for WP: from n/a through <= 1.5.3.
high 8.2 CVE-2025-32547 · published 2025-04-09
Cross-site request forgery (CSRF) in All push notification for WP (1.5.3 and older)
- Affected
- 1.5.3 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in gtlwpdev All push notification for WP all-push-notification allows Blind SQL Injection.This issue affects All push notification for WP: from n/a through <= 1.5.3.
high 7.1 CVE-2025-25092 · published 2025-03-03
Reflected cross-site scripting (XSS) in All push notification for WP (1.5.3 and older)
- Affected
- 1.5.3 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in gtlwpdev All push notification for WP all-push-notification allows Reflected XSS.This issue affects All push notification for WP: from n/a through <= 1.5.3.
Recent activity
- 2026-01-29 — closed on wordpress.org (Security Issue).
- 2026-02-04 — SQL injection disclosed (CVE-2026-0816), fix version not stated.
- 2025-04-17 — Cross-site request forgery (CSRF) disclosed (CVE-2025-32546), fix version not stated.
- 2025-04-09 — Cross-site request forgery (CSRF) disclosed (CVE-2025-32547), fix version not stated.
Get an email when All push notification for WP has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for All push notification for WP (all-push-notification) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site request forgery (CSRF) (2) · SQL injection (1) · Cross-site scripting (XSS) (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/all-push-notification (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/all-push-notification"><img src="https://laskyr.com/plugins/all-push-notification/badge.svg" alt="All push notification for WP vulnerability status"></a>