Delete Posts By URL Security & Risk Analysis

wordpress.org/plugins/delete-posts-by-url

Advanced bulk deletion of WordPress posts with multiple filtering options and powerful features for content management.

80 active installs v2.2.1 PHP 7.2+ WP 5.0+ Updated Jun 26, 2025
batch-deletebulk-deletedelete-postspost-managementurl-delete
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Delete Posts By URL Safe to Use in 2026?

Generally Safe

Score 100/100

Delete Posts By URL has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 9mo ago
Risk Assessment

The 'delete-posts-by-url' plugin v2.2.1 exhibits a generally good security posture based on the provided static analysis. The limited attack surface, with only one AJAX handler and no unprotected entry points, is a positive sign. The complete absence of dangerous functions, external HTTP requests, and file operations further strengthens its security. Furthermore, the fact that all SQL queries utilize prepared statements and there's a reasonable number of nonce and capability checks indicates adherence to common WordPress security best practices.

However, a significant concern arises from the output escaping. With 40 total outputs and only 38% properly escaped, there is a substantial risk of Cross-Site Scripting (XSS) vulnerabilities. This means that user-supplied data, if not handled carefully within the plugin, could be injected and executed in the browser of other users. The lack of recorded vulnerabilities in its history is positive but doesn't negate the identified weaknesses in output sanitization. The plugin's strengths lie in its limited attack surface and secure data handling for SQL. The primary weakness is the poor output escaping, which presents a tangible risk.

Key Concerns

  • Insufficient output escaping
Vulnerabilities
None known

Delete Posts By URL Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

Delete Posts By URL Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
25
15 escaped
Nonce Checks
2
Capability Checks
3
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

38% escaped40 total outputs
Attack Surface

Delete Posts By URL Attack Surface

Entry Points1
Unprotected0

AJAX Handlers 1

authwp_ajax_dpbu_export_deleteddelete-posts-by-url.php:37
WordPress Hooks 4
actionadmin_menudelete-posts-by-url.php:34
actionadmin_initdelete-posts-by-url.php:35
actionadmin_enqueue_scriptsdelete-posts-by-url.php:36
actionplugins_loadeddelete-posts-by-url.php:501
Maintenance & Trust

Delete Posts By URL Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedJun 26, 2025
PHP min version7.2
Downloads866

Community Trust

Rating100/100
Number of ratings1
Active installs80
Developer Profile

Delete Posts By URL Developer Profile

betterranking

1 plugin · 80 total installs

94
trust score
Avg Security Score
100/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Delete Posts By URL

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/delete-posts-by-url/assets/css/admin.css/wp-content/plugins/delete-posts-by-url/assets/js/admin.js
Script Paths
/wp-content/plugins/delete-posts-by-url/assets/js/admin.js
Version Parameters
delete-posts-by-url/assets/css/admin.css?ver=2.2.1delete-posts-by-url/assets/js/admin.js?ver=2.2.1

HTML / DOM Fingerprints

CSS Classes
dpbu-datepicker
Data Attributes
data-action="dpbu_export_deleted"
JS Globals
dpbuAdmin
FAQ

Frequently Asked Questions about Delete Posts By URL