dbcve.org
Mass Delete Unused TagsWordPress extension · Mijnpress

CVE-2023-27430

HIGH · 8.8 CVSS v3.1 Published 2023-05-18
Fix available
A fix is available. Upgrade to 3.0.0 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 Ramon Fincken Mass Delete Unused Tags plugin <= 2.0.0 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Ramon Fincken Mass Delete Unused Tags WordPress plugin versions 2.0.0 and below. The plugin lacks proper nonce validation on administrative actions, allowing attackers to craft malicious requests that trick authenticated administrators into unknowingly executing unintended operations like mass deletion of tags.

MitigationImplement WordPress nonces (wp_nonce_field, wp_verify_nonce) on all form submissions and AJAX actions within the plugin to validate request origin and intent. Alternatively, update to a patched version if released by the vendor.

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
Mass Delete Unused TagsWordPress extension
Affected:< 3.0.0

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. Locate the installed plugin
    Check your WordPress plugin directory for 'mass-delete-unused-tags', 'mijnpress-mass-delete-unused-tags', or 'ramon-fincken-mass-delete-unused-tags' folder. In WordPress admin, go to Plugins > Installed Plugins and look for 'Mass Delete Unused Tags' or similar naming.
    Affected if The plugin is present in the WordPress installation
  2. Identify the plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the 'Mass Delete Unused Tags' plugin. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file for the 'Version' header comment.
    Affected if Version is 2.0.0 or below, or less than 3.0.0
  3. Inspect the plugin for nonce implementation
    Access the plugin files via FTP or file manager. Examine the main plugin PHP file(s) for presence of wp_nonce_field, wp_nonce_url, or wp_create_nonce when generating forms or URLs. Also check for wp_verify_nonce, check_admin_referer, or wp_nonce_validate when processing requests.
    Affected if The plugin code lacks nonce generation on forms/URLs and/or lacks nonce verification on request handling
  4. Verify admin action accessibility
    Check if the plugin provides any admin pages, forms, or AJAX endpoints that perform tag deletion or similar administrative functions. Look for action parameters in URLs or form hidden fields.
    Affected if The plugin exposes administrative functions (tag deletion) without CSRF protection
  5. Check for vulnerable form submissions
    Review plugin source code for any form handling that processes administrative actions without calling wp_verify_nonce or check_admin_referer. Look for POST or GET requests that modify data.
    Affected if Forms submitting to admin actions lack nonce validation logic

Your environment is affected if the Mass Delete Unused Tags plugin is installed with version below 3.0.0 and the plugin code does not implement WordPress nonce verification on its administrative action handlers.

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 3.0.0 or later
Fixed in 3.0.0
Interim mitigation

Implement WordPress nonces (wp_nonce_field, wp_verify_nonce) on all form submissions and AJAX actions within the plugin to validate request origin and intent. Alternatively, update to a patched version if released by the vendor.

Recommended fix High confidence

Mass Delete Unused Tags version 3.0.0

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress Admin > Plugins > Installed Plugins
  3. Locate 'Mass Delete Unused Tags' by Ramon Fincken
  4. Click 'Update now' to upgrade the plugin to version 3.0.0 or later
  5. Verify the plugin was successfully updated by checking the version number in the plugins list
  6. Test that the plugin functionality works correctly after the update
Caveat Review plugin settings after upgrade as default configurations may have changed

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

Fix this in Mass Delete Unused Tags Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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