CVE-2025-32547
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a compound vulnerability in the 'All push notification for WP' WordPress plugin where Cross-Site Request Forgery (CSRF) enables a Blind SQL Injection attack. An attacker can trick a logged-in administrator into submitting a crafted request that executes arbitrary SQL queries by inferring results from application behavior differences.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck for the plugin directory at wp-content/plugins/all-push-notification-for-wp/ or search for files containing 'All push notification for WP' in plugin headers within the wp-content/plugins/ directoryAffected if The plugin directory exists in the WordPress plugins folder
-
Identify the installed plugin versionOpen the main plugin PHP file (usually named similarly to the plugin slug) and locate the 'Version:' field in the plugin header comment at the top of the fileAffected if The version number found is lower than the fixed version (if known) or if the version cannot be determined and the plugin is present
-
Confirm the plugin is activeLog into WordPress admin panel and navigate to Plugins > Installed Plugins, or query the wp_options table for the option_name 'active_plugins' to check if the plugin is in the active listAffected if The plugin appears in the list of active plugins and is enabled on the site
-
Check for CSRF vulnerability in plugin codeExamine the plugin PHP files for form submissions and admin actions. Look for code that processes $_POST, $_GET, or $_REQUEST parameters without verifying a WordPress nonce (wp_verifyNonce, wp_nonce_field, or check_admin_referer)Affected if Admin action handlers exist that process user input without nonce verification
-
Check for SQL injection vulnerability in plugin codeSearch plugin PHP files for direct SQL queries using $wpdb->query, $wpdb->get_results, or similar without $wpdb->prepare() or parameterized queries. Focus on files handling notification settings, subscriber data, or message sending functionsAffected if SQL queries accept user-supplied input (from $_POST, $_GET, or URL parameters) without using $wpdb->prepare() or equivalent prepared statements
The environment is affected if the 'All push notification for WP' plugin is installed, active, and contains admin action handlers that process user input without WordPress nonce verification and execute SQL queries without prepared statements.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataFix requires implementing WordPress nonces for CSRF protection and replacing unsafe SQL queries with prepared statements/parameterized queries to prevent SQL injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32547 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32547 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data