CVE-2025-32546
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 Reflected XSS.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the All push notification for WP plugin (versions <= 1.5.3) allows unauthenticated attackers to trick authenticated administrators into executing unintended actions via crafted requests, leading to Reflected XSS where malicious scripts are injected and executed in the context of the victim's browser session.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify if the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'All push notification for WP' or search for files containing 'all-push-notification' in /wp-content/plugins/Affected if the plugin appears in the installed plugins list
-
Check the installed plugin versionIn WordPress admin_plugins page, click on the plugin name to view version details, or inspect the plugin main PHP file header for 'Version:' tagAffected if the version number is 1.5.3 or lower
-
Verify the plugin is activeIn WordPress admin > Plugins, check if 'All push notification for WP' shows as 'Active' under the plugin statusAffected if the plugin is currently activated on the site
-
Inspect for missing nonce verification in admin actionsAccess the plugin directory (typically /wp-content/plugins/all-push-notification-for-wp/) and examine PHP files handling form submissions or URL parameters for state-changing operations; look for wp_nonce_field(), wp_verify_nonce(), or check_admin_referer() function callsAffected if form handlers or action-processing code lack nonce verification and the plugin version is <= 1.5.3
A user is affected if the 'All push notification for WP' plugin is installed with version 1.5.3 or lower and is active, especially if the plugin code lacks anti-CSRF token validation on administrative actions.
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 dataImplement anti-CSRF tokens (nonces) on all state-changing operations and forms, combined with proper output encoding and input validation to prevent the reflected XSS. Update to the latest plugin version if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32546 — 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-32546 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