dbcve.org
Delete Post RevisionsWordPress extension · Wapnepal

CVE-2023-48754

HIGH · 8.8 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to after 4.6 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 Wap Nepal Delete Post Revisions In WordPress allows Cross Site Request Forgery.This issue affects Delete Post Revisions In WordPress: from n/a through 4.6.

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 confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in the 'Delete Post Revisions' WordPress plugin by Wap Nepal. The plugin lacks proper CSRF protection (anti-CSRF tokens/nonces) in its administrative actions, allowing attackers to trick authenticated WordPress administrators into unknowingly triggering actions like deleting post revisions via maliciously crafted links or forms.

MitigationImplement WordPress nonces (wp_create_nonce, wp_verify_nonce) on all plugin admin actions and verify the referer header to ensure requests originate from the legitimate admin dashboard. This is a standard WordPress security practice for preventing CSRF attacks.

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
Delete Post RevisionsWordPress extension
Affected:<= 4.6

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. Identify plugin installation and version
    Go to WordPress Admin > Plugins and look for 'Delete Post Revisions' by Wap Nepal. Check the version number displayed below the plugin name.
    Affected if The plugin is installed and its version is 4.6 or lower.
  2. Verify plugin is active
    In WordPress Admin > Plugins, confirm the plugin shows as 'Active' underneath its name.
    Affected if The plugin is active and vulnerable to CSRF exploitation.
  3. Inspect plugin admin menu registration
    Navigate to the plugin files via FTP or file manager. Locate the main plugin PHP file and examine how admin menus are registered (look for add_menu_page, add_submenu_page, or add_management_page functions).
    Affected if The plugin registers admin menu items without apparent nonce handling.
  4. Check admin action handlers for nonce verification
    In the plugin files, locate functions handling admin actions (search for 'add_action' hooks with 'admin_init', 'admin_post', or similar). Examine whether these hooks call wp_verify_nonce or check_admin_referer.
    Affected if Admin action handlers do not verify nonces, confirming the CSRF protection is missing.
  5. Test for CSRF vulnerability manually
    While logged in as admin, inspect the plugin's settings page or delete function. Check if forms or URLs include a '_wpnonce' or 'nonce' parameter. Submit a request without this parameter and observe if the action still executes.
    Affected if Actions execute without requiring a valid nonce, indicating the CSRF guard is absent.

If the Wapnepal Delete Post Revisions plugin is installed, active, and version 4.6 or lower without nonce verification on its admin actions, the environment is vulnerable to CVE-2023-48754.

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 a release after 4.6
Interim mitigation

Implement WordPress nonces (wp_create_nonce, wp_verify_nonce) on all plugin admin actions and verify the referer header to ensure requests originate from the legitimate admin dashboard. This is a standard WordPress security practice for preventing CSRF attacks.

Recommended fix Moderate confidence

Version 4.7 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate 'Delete Post Revisions' by Wap Nepal
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update appears, manually download the latest version from the official WordPress plugin repository and reinstall
  6. 6. Verify the plugin is now running version 4.7 or higher after update

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

Fix this in Delete Post Revisions Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-48754 — 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-2023-48754 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