Beej

WordPress 3.0+ is great. It shows you your uploaded header images. 
It’s too bad it doesn’t let you delete them as well! 
The answer is here with a simple yet extremely useful little plugin called Delete Custom Header. 
Unlike WP’s “Remove Header” button, this plugin completely removes the header image data 
from the database and the files from the server.
For themes with a header option, like Twenty Ten, Twenty Eleven, etc.

Delete Custom Header

Delete uploaded header images and remove them from the database.

Marc Armengou

Security Hardener is inspired by the official WordPress hardening guide (Advanced Administration / Security / Hardening). It uses the platform’s standard functions and does not override core. Applies a prudent set of defenses:
<ul>
<li>Security headers: <code>X-Frame-Options</code>, <code>X-Content-Type-Options</code>, <code>Referrer-Policy</code>, <code>Permissions-Policy</code>, <code>COOP/CORP</code>. </li>
<li>HSTS (optional; HTTPS only). </li>
<li>Basic nonce-based CSP (optional; requires testing). </li>
<li>Disable XML-RPC and pingbacks (optional; enabled by default). </li>
<li>Hide the WordPress version in the <code><head></code>. </li>
<li>Block user enumeration via <code>/?author=</code> by returning 404. </li>
<li>Generic login errors (prevents information leakage). </li>
<li>IP-based login rate limiting with transients (configurable threshold and window). </li>
<li>Restrict the REST API to authenticated users, with a minimal allowlist for oEmbed/index.</li>
</ul>
<blockquote>
⚠️ Important: The restrict REST API option and CSP can affect integrations and plugins. Test it in staging first.
</blockquote>
Privacy: the plugin does not send data to external services or create new tables. It only uses transients to count failed login attempts.

Security Hardener

Basic hardening: secure headers, enumeration blocking, generic login errors, IP-based rate limiting, and optional restriction of the REST API.

Delete Custom Header vs Security Hardener