CVE-2025-32547: All push notification for WP · Cross-Site Request Forgery (CSRF)
Affects All push notification for WPSource CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 9 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| gtlwpdev All push notification for WP | Affected
| Fixed in– |
AI-suggested
Until a patch is available, users should consider disabling or removing the affected plugin or restricting access to trusted users only. Monitor official vendor channels for updates and apply any official fixes promptly once released.
Description
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.