Wp Bulk DeleteWordPress extension · Xylusthemes
CVE-2025-58192
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 · uneditedMissing Authorization vulnerability in Xylus Themes WP Bulk Delete wp-bulk-delete allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Bulk Delete: from n/a through <= 1.3.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 confidenceThe WP Bulk Delete plugin versions up to 1.3.6 contain a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels, likely enabling unauthorized users to perform bulk delete operations without proper authentication or authorization checks.
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
Wp Bulk DeleteWordPress extension
< 1.3.7CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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.
-
Confirm WP Bulk Delete plugin is installedCheck the WordPress plugins directory for the 'wp-bulk-delete' folder, typically at /wp-content/plugins/wp-bulk-delete/, or look for the plugin in the WordPress admin plugins listAffected if The plugin folder exists in the plugins directory
-
Identify the installed versionOpen the main plugin file (wp-bulk-delete.php) or the readme.txt file in the plugin directory and locate the version number in the plugin header commentAffected if The version listed is 1.3.6 or lower, or if no version is displayed but the plugin is present (indicating an older installation)
-
Verify AJAX action accessibilityInspect the main plugin PHP file for AJAX action handlers (functions containing 'add_action' with 'wp_ajax_' or 'wp_ajax_nopriv_') and check if they include capability checks or user authentication verification before executing delete operationsAffected if AJAX handlers for bulk delete operations lack current_user_can() checks or is_user_logged_in() verification, or use wp_ajax_nopriv_ hooks
-
Test unauthenticated access to delete functionsIf technically safe in a non-production environment, send a direct POST request to /wp-admin/admin-ajax.php with a bulk delete action (such as 'bd_delete_posts' or similar) without providing authentication credentials and observe the responseAffected if The server returns a successful delete operation response rather than an authentication error or 401/403 status
The environment is affected if the WP Bulk Delete plugin is installed with version 1.3.6 or lower, and the plugin's AJAX-based bulk delete endpoints are accessible without authentication or proper authorization checks.
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.
dbcve · scoped1.3.7
Update WP Bulk Delete to the latest version once available, or implement server-side access controls restricting admin AJAX actions to authenticated administrators only until a patch is released.
WP Bulk Delete 1.3.7
- Backup your WordPress site and database before making any changes
- Update WP Bulk Delete plugin to version 1.3.7 or later through WordPress admin dashboard (Plugins > Updates)
- Alternatively, navigate to Plugins > Installed Plugins > WP Bulk Delete and click Update Now
- After update, verify the plugin is functioning correctly by testing its core functionality
- Consider reviewing user roles and capabilities to ensure proper access controls are in place
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Bulk Delete
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58192 — 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-58192 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