WordPress plugin intelligence profile

Brightery File Lockdown

Locks down code-changing capabilities and restricts WordPress uploads to approved media types.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.0.9
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.2 · PHP 7.4
Directory statusactive
Last directory update6 Sept 20261mo ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Brightery File Lockdown version 1.0.9 as active, updated 1mo ago and tested up to WordPress 7.1.

Overview

About this plugin

Brightery File Lockdown reduces the impact of a compromised WordPress administrator account by restricting high-risk code and upload capabilities.

In standard plugin mode it:

  • Disables theme and plugin source-editing capabilities.
  • Blocks installation of new plugins and themes from wp-admin.
  • Blocks plugin and theme ZIP uploads.
  • Blocks plugin and theme deletion from wp-admin.
  • Keeps core, plugin, and theme updates configurable.
  • Restricts uploads to an explicit image, audio, and video allowlist.
  • Rejects executable, script, archive, and configuration-file extensions.
  • Rejects suspicious double extensions such as example.php.jpg.
  • Uses WordPress file-type validation plus server-side MIME detection when available.
  • Applies the same upload checks to normal uploads and sideloaded uploads.
  • Keeps a bounded local record of the latest 100 blocked security events in the WordPress database.

The plugin does not contact Brightery or any external service, does not send telemetry, and does not collect IP addresses or WordPress user IDs.

Admin-resistant Must-Use mode

A normal WordPress plugin can always be deactivated by an administrator. If your security goal is to remain active after a WordPress administrator account is compromised, use the optional Must-Use loader included in the mu directory.

org transparency and normal plugin lifecycle behavior, Brightery File Lockdown does not copy or install itself into wp-content/mu-plugins automatically.

A trusted server administrator may manually deploy the Must-Use mode using two files from this package:

  • Copy mu/brightery-file-lockdown-mu-loader.php to wp-content/mu-plugins/brightery-file-lockdown.php.
  • Create wp-content/mu-plugins/brightery-file-lockdown/ and copy includes/class-brightery-file-lockdown.php into that directory as class-brightery-file-lockdown.php.

The deployed MU loader resolves the copied engine relative to the loader’s own location. It does not rely on WP_PLUGIN_DIR or the normal plugin directory name. This lets the Must-Use protection continue loading even if the normal plugin is deactivated or its directory is renamed.

Remove both manually deployed Must-Use files with trusted filesystem access before uninstalling the normal plugin.

This plugin is a hardening layer, not a guarantee against compromise. Keep WordPress, plugins, themes, PHP, and the web server updated and apply server-level upload execution restrictions where appropriate.

Privacy

Brightery File Lockdown does not transmit data to external servers and does not collect IP addresses or WordPress user IDs. A bounded local event record may contain blocked filenames, MIME types, block reasons, and timestamps.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • file security
  • hardening
  • media
  • uploads
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.2 · PHP 7.4
Update activity6 Sept 20261mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.