by Brightery 0 (0 reviews)

Brightery File Lockdown

Name: Brightery File Lockdown
Author: Brightery

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

Brightery File Lockdown ranks #59,527 among WordPress.org plugins with 0+ active installations, is #5,907 of 6,299 in the Media category, and was last updated Sep 6, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v1.0.9 Current Version v1.0.9

Updated 1 week ago Last Update on 06 Sep, 2026

Refreshed 12 hours ago Last Refreshed on

#5,907 of 6,299 in Media Downloads -66.2% this week Actively maintained

View on WordPress.org

Rank

#59,527

+8653 this week

Active Installs

— No change

KW Avg Position

N/A

— No change

Downloads

+6 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

33,714

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 8 more installs to reach 10+

Rank Changes

Current #59,527

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.9
Last Updated: Sep 06, 2026
Requires WP: 6.2+
Tested Up To: 7.1
PHP Version: 7.4 or higher
Author: Brightery

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

file security hardening media security uploads

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,752

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,007

Jetpack - WP Security, Backup, Speed, & Growth

3M+ installs

#18

Advanced Custom Fields (ACF®)

2M+ installs

#28

Image Optimization - Compress Images and Convert to WebP or AVIF

Regenerate Thumbnails

1M+ installs

#64

Smush – Image Optimization, Compression, Lazy Load, WebP & CDN

1M+ installs

#65

Imagify Image Optimization: Optimize Images | Compress & Convert to WebP/AVIF

View all Media plugins

Frequently Asked Questions

Common questions about Brightery File Lockdown

In standard mode, yes. This respects the normal WordPress plugin lifecycle. For a compromised-admin threat model, manually deploy the included MU loader and engine copy using trusted server access.

No. The WordPress.org package does not automatically create or modify files in wp-content/mu-plugins or other content directories.

The Must-Use loader is intentionally independent of the normal plugin directory. Deploying a copy of the engine beside the loader means the loader does not hardcode the normal plugin folder or rely on WP_PLUGIN_DIR.

Common image, audio, and video formats remain allowed. PDF is disabled by default and can be explicitly enabled in wp-config.php.

Updates are allowed by default. They can be disabled through server-side configuration constants when a site owner intentionally wants a stricter immutable-code workflow.

No. There are no telemetry, tracking, remote API, license-check, or external service calls.

The latest 100 blocked events are kept in a non-autoloaded WordPress option on the local site. Entries can contain the blocked filename, claimed MIME type, reason, and event time. IP addresses and user IDs are not collected.

The plugin removes its local blocked-event option during normal WordPress uninstall. Any manually deployed Must-Use files must be removed separately using trusted filesystem access.