WordPress plugin · Updated daily · Source: Wordfence Intelligence

Web Push Notifications vulnerabilities: affected versions and fixes

Web Push Notifications has 10,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Web Push Notifications at a glance

  • 5 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Jul 22, 2026.
  • Ranked #2059 by popularity on WordPress.org (10,000+ active installs).
  • The latest version is 4.41.0 (released Jul 28, 2026). The most recent security fix shipped in 4.39.0.
  • 1 vulnerability has no fix yet. Check the list below to see whether it affects how you use the plugin.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Web Push Notifications version

Enter the Web Push Notifications version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Web Push Notifications”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Web Push Notifications”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (4.41.0). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Web Push Notifications vulnerabilities

  • Web Push Notifications <= 4.39.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'webpushr_notification_title' Post Meta Parameter

    Cross-site scripting (XSS) · CVE-2026-9729

    Affected versions: ≤ 4.39.0

    Fixed in: No fix yet

    Severity: Medium 6.4 · Disclosed Jul 22, 2026

  • Webpushr <= 4.38.0 - Unauthenticated Information Exposure

    Information disclosure · CVE-2026-24536

    Affected versions: ≤ 4.38.0

    Fixed in: 4.39.0

    Severity: Medium 5.3 · Disclosed Jan 25, 2026

  • Webpushr <= 4.35.0 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-34369

    Affected versions: ≤ 4.35.0

    Fixed in: 4.36.0

    Severity: Medium 6.1 · Disclosed May 3, 2024

  • Webpushr <= 4.34.0 - Missing Authorization to Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-5620

    Affected versions: ≤ 4.34.0

    Fixed in: 4.35.0

    Severity: High 7.2 · Disclosed Nov 6, 2023

  • Webpushr <= 4.34.0 - Cross-Site Request Forgery to Local File Inclusion via menu

    Cross-site request forgery (CSRF) · CVE-2023-35041

    Affected versions: ≤ 4.34.0

    Fixed in: 4.35.0

    Severity: High 8.8 · Disclosed Oct 19, 2023

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Jul 22, 2026.

Most common weaknesses in Web Push Notifications

Cross-site scripting (XSS)

3 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Information disclosure

1 issue

Data that should stay private, such as user details or configuration values, can be read from outside.

Cross-site request forgery (CSRF)

1 issue

If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.

Frequently asked questions

Is Web Push Notifications safe to use?

Web Push Notifications is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (4.41.0) and turn on automatic updates. That said, 1 issue has no fix yet, so check the list below.

How do I find which version of Web Push Notifications my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesWeb Push Notifications on WordPress.org