dbcve.org
Push Notifications For WordpressWordPress extension · Delitestudio

CVE-2021-20846

HIGH · 8.8 CVSS v3.1 Published 2021-11-24
Fix available
A fix is available. Upgrade to 6.0.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-site request forgery (CSRF) vulnerability in Push Notifications for WordPress (Lite) versions prior to 6.0.1 allows a remote attacker to hijack the authentication of an administrator and conduct an arbitrary operation via a specially crafted web page.

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 · high confidence

Cross-site request forgery (CSRF) vulnerability in the Push Notifications for WordPress (Lite) plugin allows remote attackers to execute arbitrary administrative actions by tricking a logged-in administrator into visiting a maliciously crafted web page. The attack exploits the lack of anti-CSRF tokens (nonces) in the plugin's admin functionality, enabling session hijacking of the administrator's authenticated session.

MitigationUpdate the Push Notifications for WordPress (Lite) plugin to version 6.0.1 or later, which should include proper CSRF token validation. As a temporary measure, administrators should avoid clicking untrusted links while logged into WordPress admin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Push Notifications For WordpressWordPress extension
Affected:< 6.0.1

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Push Notifications for WordPress (Lite) plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the wp-content/plugins directory for a folder related to push notifications by Delitestudio
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin > Plugins, locate the Push Notifications plugin and view the version number displayed in the plugin list, or check the plugin's main PHP file or readme.txt for the Version header
    Affected if Version is displayed as below 6.0.1 or the Version header cannot be found (which may indicate an old/unmaintained version)
  3. Confirm the vendor is Delitestudio
    Verify the plugin developer is Delitestudio by checking the plugin description or author field in the WordPress plugins list, as other push notification plugins may share similar names
    Affected if The plugin is developed by Delitestudio and matches the affected product name

A user is affected if the Delitestudio Push Notifications for WordPress (Lite) plugin is installed with a version number lower than 6.0.1, making the admin functionality vulnerable to CSRF attacks through missing nonce validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 6.0.1 or later
Fixed in 6.0.1
Interim mitigation

Update the Push Notifications for WordPress (Lite) plugin to version 6.0.1 or later, which should include proper CSRF token validation. As a temporary measure, administrators should avoid clicking untrusted links while logged into WordPress admin.

Recommended fix High confidence

6.0.1

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Push Notifications for WordPress' or 'Push Notifications for WordPress Lite'
  4. Check the current version - if below 6.0.1, an update is needed
  5. Click 'Update Now' or navigate to Plugins > Add New and search for 'Push Notifications for WordPress' to install version 6.0.1 or latest available
  6. After update, verify the plugin version is 6.0.1 or higher in Plugins > Installed Plugins

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Push Notifications For Wordpress Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20846 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-20846 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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