Security readout for executives and security teams
Plain-English summary
A WordPress plugin used for push notifications has a high-severity flaw. On sites running All push notification for WP through version 1.5.3, an attacker could abuse a CSRF weakness to trigger blind SQL injection if a user interaction occurs. The main business risk is sensitive database exposure, with limited availability impact noted.
Executive priority
Treat this as high priority for any WordPress site using the plugin, especially sites holding customer or operational data. The priority drops for environments where the plugin is absent. Because no fix is named in the supplied evidence, remediation planning should start with exposure confirmation and vendor guidance tracking.
Technical view
CVE-2025-32547 is reported as CWE-352 in gtlwpdev All push notification for WP. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L, scoring 8.2. Sources describe CSRF leading to blind SQL injection for versions up to and including 1.5.3. No exploit procedure or fixed version is provided in the supplied bundle.
Likely exposure
Exposure is likely limited to WordPress installations with the all-push-notification plugin installed at version 1.5.3 or earlier. The supplied data does not identify other affected products or hosted service exposure.
Exploitation context
The bundle does not show CISA KEV listing or other evidence of active exploitation. The CVSS vector indicates network reachability, low attack complexity, no privileges required, and required user interaction, consistent with a CSRF-assisted attack path.
Researcher notes
The public bundle supports CSRF to blind SQL injection but does not include endpoint details, proof-of-concept status, exploit telemetry, or a named patch. Avoid assuming exploitation in the wild. Focus validation on plugin presence, versioning, advisory follow-up, and suspicious plugin-adjacent request patterns.
Mitigation direction
- Inventory WordPress sites for All push notification for WP and installed version.
- If version is 1.5.3 or earlier, prioritize vendor guidance review.
- If no fixed release is available, disable or remove the plugin where feasible.
- Limit WordPress administrator sessions and avoid untrusted links while logged in.
- Monitor vendor, Patchstack, and WordPress plugin channels for remediation updates.
Validation and detection
- Confirm whether all-push-notification is installed on each WordPress property.
- Record plugin version and compare against the reported affected range through 1.5.3.
- Check whether vendor or Patchstack guidance identifies a fixed version or workaround.
- Review web and database logs for unusual plugin-related activity.
- Confirm CISA KEV status remains negative before reporting active exploitation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-32547 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L2.84.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.