

Main settings page with super user configuration
🛡️ WordPress Security and Maintenance That Prevents Problems Before They Happen
Every day, WordPress sites are compromised through supply chain attacks. A trustworthy plugin developer has their account hacked, malicious code ships as an “update”, and thousands of sites auto-install it within hours. Fuerte-WP protects your site when developers cannot protect their own update systems.
Fuerte-WP combines four defenses in one lightweight plugin: update management, admin oversight, login security, and two-factor authentication. It is built for agencies, e-commerce stores, and anyone who manages WordPress sites and needs to sleep at night.
🚨 CRITICAL: SUPPLY CHAIN ATTACK AND MALICIOUS UPDATE PROTECTION
A supply chain attack happens when an attacker compromises a developer account and pushes a malicious update that thousands of sites auto-install before anyone notices. When you learn an attack is in progress, you need to act in minutes, not days.
Fuerte-WP gives you three update modes so you can react correctly:
This is not a generic “disable updates” toggle. Deferred and Blocked are separate, intentional controls, so you can hold one compromised plugin back while the rest of the site keeps updating normally.
⚡ AUTO-UPDATE MANAGEMENT FOR CORE, PLUGINS, THEMES, AND TRANSLATIONS
Granular control over every update channel:
You can configure this once on your main site and reuse the same file-based configuration across every site you manage.
👑 ADMINISTRATOR OVERSIGHT AND ACCESS CONTROL
Most WordPress security plugins assume the administrator is the threat. Fuerte-WP assumes the administrator is trusted but busy, and that you want to protect them from themselves and from each other.
edit.php (Posts, Pages, and custom post types) and index.php are hide-only so you never strand a non-super user on a blank screen. Single-purpose core scripts (themes.php, tools.php, plugins.php) block by $pagenow. Plugin pages block by their ?page= query argument.🔒 LOGIN SECURITY (OPTIONAL, ON BY DEFAULT)
Brute force attacks against wp-login.php and XML-RPC are the most common way WordPress sites are compromised. Fuerte-WP ships with a full login hardening suite:
wp-login.php and wp-admin paths so automated bots that scan for those endpoints find nothing. Your real login URL is whatever you choose.🔐 TWO-FACTOR AUTHENTICATION (2FA) FOR ADMINS
Since version 1.10.0, Fuerte-WP bundles the official WordPress Two-Factor library and enforces a safe provider policy:
WP_DEBUG.Enforce 2FA for Administrators is on by default. Administrators and Super Admins are challenged with an emailed code at login even before they set up an authenticator app. Each admin can switch to TOTP from their own profile page. Enforcement is read-only: it never writes to user meta, so unchecking the box releases admins immediately. Fuerte super users always bypass enforcement.
Crash-safe coexistence: if you already run the standalone Two-Factor plugin, Fuerte-WP detects it and steps aside. No class-redeclare fatal, no duplicate provider screens.
Operator escape hatch: define FUERTEWP_DISABLE_2FA in wp-config.php to skip the bundled library entirely.
🛠 REST API, XML-RPC, AND APP PASSWORD HARDENING
Modern WordPress exposes several attack surfaces beyond the login form:
📧 EMAIL CONTROLS AND RECOVERY
WordPress sends a lot of email. Fuerte-WP lets you redirect and silence it:
wp_mail() (falls back to no-reply@<your-domain> when left empty)🌐 MULTISITE, PERFORMANCE, AND DEVELOPER FRIENDLINESS
$fuertewp in wp-config-fuerte.php for mass deployment. File config wins over the database, so the same settings ship to every site without touching the admin UI🔧 HOW FUERTE-WP WORKS
Fuerte-WP follows a single-source-of-truth model. Configuration lives in one normalized array and is read the same way everywhere:
wp-config-fuerte.php file first, then falls back to the database option saved by the admin UI. File always wins.FUERTEWP_FORCE to enforce even on super users, or FUERTEWP_DISABLE to switch the whole plugin off without uninstalling.Because the enforcer reads one normalized array, there is no drift between what the admin UI shows and what the site enforces. After editing config logic in code, bust the transient with delete_transient('fuertewp_config') so the new rules take effect.
📁 FILE-BASED CONFIGURATION FOR MASS DEPLOYMENT
For agencies and platform teams, Fuerte-WP can be configured entirely from a file, with no admin UI clicks. Drop a wp-config-fuerte.php file in your ABSPATH directory defining a $fuertewp array:
`
<?php
$fuertewp = array(
‘general’ => array( ‘sender_email_enable’ => true ),
‘super_users’ => array( ‘[email protected]’ ),
‘auto_updates’ => array(
‘core’ => true, ‘plugins’ => true, ‘themes’ => true,
‘translations’ => true, ‘frequency’ => ’12h’,
),
‘restrictions’ => array(
‘disable_theme_editor’ => true,
‘disable_plugin_editor’ => true,
‘restapi_disable_app_passwords’ => true,
‘disable_xmlrpc’ => true,
),
‘login_security’ => array( ‘login_security_enable’ => true, ‘two_factor_enable’ => true ),
);
`
Commit this file to your deployment pipeline and every site in your fleet ships the same security baseline. The admin UI still renders for inspection, but saved values never override the file. This is the recommended path for WordPress multisite networks and managed-hosting platforms.
📋 SECURITY HARDENING CHECKLIST
Fuerte-WP ships with safe defaults so a fresh install is already hardened. The following are on by default and can be toggled on the Restrictions and Login Security tabs:
Review the Restrictions tab after your first install and adjust to your workflow.
🎯 PERFECT FOR:
⚡ INSTALL IN SECONDS, PROTECT FOR YEARS